Integrated cloud system with lightweight gateway for premises automation

ABSTRACT

Systems and methods include a system comprising a cloud hub located in a premises. The cloud hub comprises adapters coupled to premises devices, and the cloud hub is configured as a gateway for the premises devices. A virtual gateway is located in a cloud server environment and coupled to the cloud hub. The virtual gateway is configured as a server-side abstraction of the cloud hub. The cloud hub and the virtual gateway are configured as an automation platform that maintains state data of the premises devices, controls interaction among the premises devices, and monitors and manages the premises devices. A security system coupled to the virtual gateway. The security system includes security system components.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of United States (U.S.) patentapplication Ser. No. 15/198,855, filed on Jun. 30, 2016, now U.S. Pat.No. 10,530,839.

This application claims the benefit of U.S. Patent Application No.62/186,925, filed Jun. 30, 2015.

This application claims the benefit of U.S. Patent Application No.62/186,974, filed Jun. 30, 2015.

This application claims the benefit of U.S. Patent Application No.62/186,696, filed Jun. 30, 2015.

This application claims the benefit of U.S. Patent Application No.62/186,825, filed Jun. 30, 2015.

This application claims the benefit of U.S. Patent Application No.62/186,857, filed Jun. 30, 2015.

This application is a divisional application of U.S. patent applicationSer. No. 15/198,531, filed Jun. 30, 2016, now U.S. Pat. No. 11,190,578.

This application is a continuation in part application of U.S. patentapplication Ser. No. 15/196,646, filed Jun. 29, 2016, now abandoned.

This application is a continuation in part application of U.S. patentapplication Ser. No. 12/189,780, filed Aug. 11, 2008, now abandoned.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/531,757, filed Jun. 25, 2012, now abandoned.

This application is a continuation in part application of U.S. patentapplication Ser. No. 12/197,958, filed Aug. 25, 2008, now U.S. Pat. No.10,721,087.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/334,998, filed Dec. 22, 2011, now U.S. Pat. No.9,531,593.

This application is a continuation in part application of U.S. patentapplication Ser. No. 12/539,537, filed Aug. 11, 2009, now U.S. Pat. No.10,156,959.

This application is a continuation in part application of U.S. patentapplication Ser. No. 14/645,808, filed Mar. 12, 2015, now U.S. Pat. No.10,127,801.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/104,932, filed May 10, 2011, now abandoned.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/929,568, filed Jun. 27, 2013, now U.S. Pat. No.10,444,964.

This application is a continuation in part application of U.S. patentapplication Ser. No. 14/628,651, filed Feb. 23, 2015, now U.S. Pat. No.10,091,014.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/718,851, filed Dec. 18, 2012, now U.S. Pat. No.10,156,831.

This application is a continuation in part application of U.S. patentapplication Ser. No. 12/972,740, filed Dec. 20, 2010, now U.S. Pat. No.9,729,342.

This application is a continuation in part application of U.S. patentapplication Ser. No. 13/954,553, filed Jul. 30, 2013, now U.S. Pat. No.11,582,065.

This application is a continuation in part application of U.S. patentapplication Ser. No. 14/943,162, filed Nov. 17, 2015, now U.S. Pat. No.10,062,245.

This application is a continuation in part application of U.S. patentapplication Ser. No. 15/177,915, filed Jun. 9, 2016, now U.S. Pat. No.11,316,958.

TECHNICAL FIELD

The embodiments described herein relate generally to networking and,more particularly, to premises automation systems and methods.

BACKGROUND

There is a need for systems and methods that integrate cloud servicesand internet-connected devices with a user interface and othercomponents and functions of a service provider system. This integrationwould enable third party and/or other connected devices (e.g., smartdoor bells, door locks, garage door operators, cameras, thermostats,lighting systems, lighting devices, etc.), and third party services tocontrol or trigger automations in the service provider system usingcomponents and functions of the service provider system. This wouldenable end-users to integrate and use their previously-standaloneinternet-connected devices with each other as well as with their serviceprovider-based service.

INCORPORATION BY REFERENCE

Each patent, patent application, and/or publication mentioned in thisspecification is herein incorporated by reference in its entirety to thesame extent as if each individual patent, patent application, and/orpublication was specifically and individually indicated to beincorporated by reference.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system including a Cloud Hub (FlexCore)and

Virtual Gateway, also referred to herein as the Lightweight Gateway(LWG), under an embodiment.

FIG. 2 is a block diagram of a system including a Cloud Hub and VirtualGateway showing the premises, service provider, and mobile environments,under an embodiment.

FIG. 3 is a flow diagram for Cloud Hub device installation, under anembodiment.

FIG. 4 is a block diagram showing communications of the LGW, under anembodiment.

FIG. 5 is a block diagram showing an object model of the LGW, under anembodiment.

FIG. 6 is a block diagram of the application architecture, under anembodiment.

FIG. 7 is a flow diagram for device state change, under an embodiment.

FIG. 8 is a flow diagram for media upload, under an embodiment.

FIG. 9 is a flow diagram for live video, under an embodiment.

FIG. 10 is a flow diagram for event trigger notification, under anembodiment.

FIG. 11 is a flow diagram for activation iHub, under an embodiment.

FIG. 12 is a flow diagram for activation LWG, under an embodiment.

FIG. 13 is a flow diagram for app sign-in (Web/Android app) iHub, underan embodiment.

FIG. 14 is a flow diagram for app sign-in (Web/Android app) LWG, underan embodiment.

FIG. 15 is a flow diagram for app session, device event (Web/Androidapp), under an embodiment.

FIG. 16 is a flow diagram for app sign-in (iOS) iHub, under anembodiment.

FIG. 17 is a flow diagram for app sign-in (iOS) LWG, under anembodiment.

FIG. 18 is a flow diagram for app session, device event (iOS app), underan embodiment.

FIG. 19 is a flow diagram for LWG remote arm, under an embodiment.

FIG. 20 is a flow diagram for iHub reboot, under an embodiment.

FIG. 21 is a flow diagram for iHub disconnect, under an embodiment.

FIG. 22 is a block diagram of the integrated security system, under anembodiment.

FIG. 23 is a block diagram of components of the integrated securitysystem, under an embodiment.

FIG. 24 is a block diagram of the gateway including gateway software orapplications, under an embodiment.

FIG. 25 is a block diagram of components of the gateway, under anembodiment.

FIG. 26 is a block diagram of IP device integration with a premisenetwork, under an embodiment.

FIG. 27 is a block diagram of IP device integration with a premisenetwork, under an alternative embodiment.

FIG. 28 is a block diagram of a touchscreen, under an embodiment.

FIG. 29 is an example screenshot of a networked security touchscreen,under an embodiment.

FIG. 30 is a block diagram of network or premise device integration witha premise network, under an embodiment.

FIG. 31 is a block diagram of network or premise device integration witha premise network, under an alternative embodiment.

FIG. 32 is a block diagram of the Integrated Cloud System (ICS) orplatform, under an embodiment.

FIG. 33 is a flow diagram for Service Association, under an embodiment.

FIG. 34 is a flow diagram for Service Disassociation, under anembodiment.

FIG. 35 is a flow diagram for Card UI Interactions, under an embodiment.

FIG. 36 is an example rules interface for controlling triggers andactions involving third party devices integrated in the ICS, under anembodiment.

FIG. 37 is an example of a triggers portion of a rules interface forthird party services integrated with the ICS, under an embodiment.

FIG. 38 is another example of an actions portion of a rules interfacefor integrated third party devices, under an embodiment.

DETAILED DESCRIPTION

Embodiments include a cloud hub located in a premises, and the cloud hubcomprises adapters configured for coupling to premises devices. Thecloud hub is configured as a gateway for the premises devices. Thesystem includes a virtual gateway located in a cloud server environmentand coupled to the cloud hub. The virtual gateway is configured as aserver-side abstraction of the cloud hub. The cloud hub and the virtualgateway are configured as an automation platform that maintains statedata of the premises devices, controls interaction among the premisesdevices, and monitors and manages the premises devices.

Embodiments include a system comprising a cloud hub located in apremises. The cloud hub comprises adapters coupled to premises devices,and the cloud hub is configured as a gateway for the premises devices. Avirtual gateway is located in a cloud server environment and coupled tothe cloud hub. The virtual gateway is configured as a server-sideabstraction of the cloud hub. The cloud hub and the virtual gateway areconfigured as an automation platform that maintains state data of thepremises devices, controls interaction among the premises devices, andmonitors and manages the premises devices. A security system coupled tothe virtual gateway. The security system includes security systemcomponents.

FIG. 1 is a block diagram of a system including a Cloud Hub and VirtualGateway, also referred to herein as the Lightweight Gateway (LWG) orFlexCore, under an embodiment. The “Cloud Hub” is a dual purpose Z-Waveand Wi-Fi Access Point configured to enable full premises automation(e.g., Tier-1 sites). The Cloud Hub device couples or connects to thepremises broadband connection and operates as a gateway for Z-Wave andcamera traffic. Cloud Hub enables Z-Wave for premises and customerpremises equipment (CPE) that do not currently support it, and providesa Wi-Fi sandbox for Direct Cameras. An example of a hardware platformconfigured as a Cloud Hub is the Sercomm NA301v2 device, but theembodiment is not so limited as numerous other devices can serve as theCloud Hub. The detailed description herein includes aspects of thesoftware and firmware of the Cloud Hub along with server and clientapplication software.

FIG. 2 is a block diagram of a system including a Cloud Hub and VirtualGateway showing the premises, service provider, and mobile environments,under an embodiment. The system of an embodiment includes the gateway(FlexCore) in the premises (e.g., home, office, etc.), and the gatewayis coupled to a LWG in the operator (server/cloud) domain. The gatewayincludes one or more of a camera adapter to integrate premises cameras,an IP adapter to integrate premises IP devices, and a ZigBee protocoland hardware driver to integrate premises ZigBee devices. Components ofthe gateway of an embodiment are coupled to a radio frequency (RF)bridge as appropriate to a configuration of devices in the premises, andthe RF bridge integrates additional premises devices (e.g., Z-Wavedevices, proprietary devices, etc.) into the system.

The LWG and cloud-based infrastructure of an embodiment uses an existingservice provider infrastructure, security, performance, and APIs, alongwith system components that are separated into modules executed ondistributed in-premises systems. The LWG and cloud-based infrastructureincludes a pluggable architecture that enables new device protocols andRF technologies to be added without the need to overhaul the coreinfrastructure. Use of a relatively small memory footprint on the CPEenables the infrastructure to execute on many devices, and thisrefactoring of local versus cloud services provides a virtual device(e.g., Internet of Things (IOT), etc.) gateway service that pushes asmuch as possible to the cloud while maintaining local performance andoffline capabilities.

An embodiment includes a Lightweight Gateway (LWG) that is configured asthe server-side abstraction for the Cloud Hub. The LWG is subordinate tothe gateway object, and interacts with the server and the Cloud Hubdevice in much the same way that a RISSecurityPanel class does. As such,an embodiment re-factors the common code out of RISSecurityPanel into aclass that both RISSecurityPanel and the Cloud Hub device can use. A newdevice definition is created for this type of device, and variouschanges to the StandardGateway class to control and manage theadditional communication channel with the new device.

The Session Server configuration uses a gateway registry service toroute incoming UDP packets from the CPE to the proper lightweightgateway instance via a one-to-one mapping of CPE-unique IDs to site IDs.With the addition of the Cloud Hub, a second CPE-unique ID is mapped tothe same LWG instance as the primary security, monitoring and automation(SMA) client's CPE-unique ID. This is accomplished by leveraging theDevice Registry, which maintains a mapping of CPE ID and device type tosite ID. Further, the session server is modified to use this DeviceRegistry to properly route income packets.

Regarding client application software or applications, the clientsinclude UX additions to present the new Cloud Hub device. When the CloudHub is present, UX flow will potentially be different. For example, on aCloud Hub system, Z-Wave devices are not added until the Cloud Hub isadded. Also, deleting the Cloud Hub includes deleting the associatedZ-Wave devices, and this uses special UX messaging. The activation appand the installer app will also need new flows for installing andmanaging these devices.

The Cloud Hub firmware of an example embodiment includes but is notlimited to the following components: SMA Client: an always-on (i.e.,always-TCP-connected) SMA client, supporting AES-256 encryption; ezwLib:port of the Icontrol embedded Z-Wave stack; Bootstrap Client for securebootstrap of the master key, and then secure provisioning of the SMAServer connection information and initialization information; LED Driverto drive CPE LED that displays Server connectivity and Z-Wave status(CPE-dependent); Firmware Update Logic for fault-tolerant updates of thefull CPE image (CPE-dependent); detailed/tunable error logging; Reset ToFactory Default Logic for factory-default Z-Wave (erase node cache andsecurity keys), WiFi (disable sandbox, reset SSID/PSK; CPE-dependent),and de-provision (erase SMA Server info).

In an example configuration, server-CPE communication is over SMAv1protocol, except for bootstrapping and provisioning which uses theOpenHome “Off-Premise Bootstrap Procedure.” On the CPE, the OS andnetwork layer (Wi-Fi sandbox, WPS, routing, etc.) are provided andmanaged by the CPE OEM (e.g., Sercomm). Wi-Fi provisioning and trafficis handled by the CPE OEM (e.g., Sercomm) without Cloud Hubintervention/signaling, except with respect to enabling/disabling andresetting to defaults.

The Cloud Hub device installation and bootstrap mechanism performs oneor more of the following: associate the device with an existing site;securely deliver the SMA communication configuration, including masterkey, SMA server address, and network ports. An embodiment includes anoff-premise bootstrapping procedure, also used for bootstrappingtunneling cameras, that includes a three-step process.

FIG. 3 is a flow diagram for Cloud Hub device installation, under anembodiment. During a first step, the Cloud Hub couples or connects tothe Registry Gateway (e.g., via the pre-configured Registry Gateway URL)and retrieves its assigned siteID and the Credential Gateway URL. Asecond step includes the Cloud Hub retrieving its master key from theCredential Gateway using its siteID and Activation Key. A third stepincludes the Cloud Hub retrieving Session Gateway Information from theCredential Gateway. At the end of the Bootstrap phase, the Cloud Hub ofan embodiment has obtained its master key and its Session Gatewayaddress from the iControl Gateway. Each of these steps is described indetail below.

During normal operation, the CPE performs the first and third processeson every start-up/restart. The second process is followed only if thereis no previously stored master key. Hence, security credentials can bere-bootstrapped by invalidating the existing master key.

The Cloud Hub uses the first step process or procedure at least toretrieve its SiteID and Credential Gateway URL.

Purpose Retrieve Credential Gateway URL and siteID using Cloud HubSerial Number as input Message Format HTTPS GET /<Registry GatewayURL>/<Serial Number> HTTP/1.1 Authentication None Mandatory Request HostHeaders <registryEntry serial=“<Serial Number>” href=“/<Registry GatewayURL>/<Serial Number>”> <functions>...</functions > 200 OK response<siteId><siteID></siteId> <gatewayUrl><Credential GatewayURL></gatewayUrl> </registryEntry> Error responses Standard HTTPresponse codes (e.g., 404) Example Requesthttps://adminsirius3.icontrol.com/rest/icontrol/registry/serial/00603504026c <registryEntry serial=“00:60:35:04:02:6c”href=“/rest/icontrol/registry/serial/00603504026c”> <functionscount=“1”> <function name=“delete”action=“/rest/icontrol/registry/serial/00603504026c” Example 200 OKmethod=“DELETE”> Response </functions> <siteId>00603504026c</siteId><gatewayUrl>http://gsess-sirius3.icontrol.com/gw</gatewayUrl></registryEntry> Variable Name Format Description/Notes Registry GatewayURL Pre-configured in Cloud Hub firmware URL Serial Number 12 byte hexstring Pre-configured in Cloud Hub firmware siteID 12-20 digit alphanumeric string gatewayUrl URL prefix Prefix to use for Pending MasterKey and otherwise known as protocol:host[:port]/p Connect Info requests.CredentialGatewayU ath RL

The Cloud Hub uses the second step process or procedure at least toretrieve its Pending Master Key. If the Master Key is alreadyestablished from a previous successful Retreieve Credital procedure,this step is optional.

Purpose Retrieve device-specific Master Key using its siteID, serialnumber and Activation Key as inputs Message Format HTTPS POST/<CredentialGatewayURL>/GatewayService/<siteID>/PendingDevi ceKey HTTP/1.1Authentication None Mandatory Request Host, Content-Length, Content-Type(application/x-www-form- Headers urlencoded ) POST body serial=<SerialNumber>&activationkey=<ActivationKey> 200 OK response <pendingPaidKeymethod=“server” expires=“<pending master key with pending masterexpiration epoch millisecs>” ts=“<current epoch millisecs>” keykey=“<master key>” partner=“icontrol”/> 200 OK response Gateway respondswith a method=“retry” if the Cloud Hub is not with retry yet activatedwithin the system. Response includes timeout for retry. <PendingPaidKeymethod=“retry” expires=“<retry epoch millisecs>” ts=“<current epochmillisecs>” partner=“icontrol”/> Other HTTP Standard HTTP error responsecodes for example 5xx indicate a responses temporary server issue andCloud Hub devices should perform an automatic retry in randomized 10minute backoff Example POST bodyserial=555500000010&activationkey=AABB12345678 Example 200 OK<pendingPaidKey method=“server” expires=“1308892493528” with pending keyts=“1308849293540” key=“398341159498190458” Responsepartner=“icontrol”/> Example 200 OK <pendingPaidKey method=“retry”expires=“1308849242148” response with retry ts=“1308849122148”partner=“icontrol”/> Variable Name Format Description/NotesCredentialGatewayU Hostname[port] Retrieved via Step 1 - Retrieve RLGateway URL and SiteID siteID 12 byte hexadecimal string Retrieved viaStep 1 - Retrieve Gateway URL and SiteID ActivationKey 10+ digit alphanumeric Pre-configured in Cloud Hub, string generated by manufacturerand printed on device ‘method’ (in 200 OK String “server” or “retry”body) ‘key’ (in 200 OK Alphanumeric string Pending key returned byGateway in body) 200 OK body ‘ts’ (in 200 OK body) Numeric stringGateway's timestamp in UTC time ‘expires’ (in 200 OK Numeric string UTCtime when the current pending body) key expires Pending Key Alphanumericstring Initial key retrieved from Gateway that is not yet confirmed withthe Gateway. SharedSecret or Alphanumeric string Pending key becomesmaster key <SharedSecret> after successful connection to Gateway (seebelow)

During Cloud Hub activation, the Gateway responds to a Cloud Hub'srequest for Credential with 200 OK containing the PendingPaidKey XMLbody (with method=“server”) with a pending key field. The pending keyfield becomes active once the Cloud Hub connects to the Gateway over theSMA channel and is authenticated by using the pending key to encrypt theinitial SMA exchange. Once authenticated (via a successful SMA sessionwith the Gateway), the key is no longer pending and instead becomesactive, or otherwise known as the Cloud Hub's<SharedSecret> or masterkey. The active master key (“<SharedSecret>”) will not automaticallyexpire; however, the Gateway may update a Cloud Hub's<SharedSecret>.Once a pending key becomes active, subsequent requests for thePendingDeviceKey will receive method=“retry” responses unless a newactivation process is initiated (this can be done by administrators andinstallers via the iControl admin and portal applications).

If the Cloud Hub does not connect to the server over the SMA channel andget authenticated using the key by the “expires” time specified in thePendingPaidKey XML body, then the pending key will expire and no longerbe valid.

While Cloud Hub activation is underway, each request for thePendingPaidKey will receive a different key in the response, causing theprevious pending key to be replaced with the new one. Upon a factoryreset, the device will forget its key and return to the bootstrapprocess of polling for a PendingDeviceKey.

The Cloud Hub uses the third step process or procedure at least toretrieve Session Gateway Info, which includes SMA Gateway address.

Purpose Retrieve SMA Gateway hostname and port from Credential GatewayMessage Format HTTPS GET/<gatewayUrl>/GatewayService/<siteID>/connectInfo HTTP/1.1Authentication None Mandatory Host Request Headers <connectInfo>    <session host=<Session Gateway host> port=[port] /><riseventPort1=‘[port]’ eventPort2=‘[port]’ controlPort1=‘[port]’controlPort2=‘[port]”/> 200 OK response     <xmpp host=<XMPP Gatewayhost> port [port] /> (ignored) </connectInfo> Error responses StandardHTTP response codes (e.g., 404) <connectInfo> <sessionhost=‘gsess-aristotleqapicontrol.com’ port=‘443’/><riseventPort1=‘11083’ eventPort2=‘11083’ controlPort1=‘11084’controlPort2=‘11084’/> Example 200 OK <xmpphost=‘gsess-aristotleqapicontrol.com’ port=‘5222’/><media Responseurl=‘https://media-aristotleqap.icontrol.com/gw/GatewayService’/></connectInfo> VariableName Format Description/Notes gatewayUrl https://hostname[:port]/pathRetrieved Via Step 1 - Retrieve Gateway URL and SiteID siteID 12-20 charalpha numeric string Retrieved Via Step 1 - Retrieve Gateway URL andSiteID XMPP Gateway Hostname and port These variables should behost:port IPAddress and port ignored by the Cloud Hub. Session GatewayHostname Host and command port to use host for SMA communication withthe Gateway. session:port port This port variable should be ignored bythe Cloud Hub. ports on Session Gateway host to which SMA async eventsris:eventPort1/2 port should be sent ris:controlPort1/2 port ports onSession Gateway host for establishing the SMA control channel

The Cloud Hub of an embodiment is a broadband-connected device, and itattempts to maintain an always-on TCP/IP connection with the server.Therefore, there is no need for a shoulder-tap mechanism, as is providedvia SMS on typical tier-1 systems. No “wake-up” message is used as theCloud Hub is effectively always awake. With conventional Tier-1 systems,the server tears down the TCP connection after several minutes ofinactivity; for Cloud Hub, the TCP connection should stay up for as longas possible, with periodic server-originated SMA heartbeat messages (SMARequest Type 0), so that the CPE can supervise the connection as beingtruly active.

Incoming messages (e.g., UDP) to the session server and the DeviceRegistry from the CPE are routed to the LWG instance associated with agiven site ID. In a conventional current pre-CloudHub configuration, thesession server uses the Gateway Registry, which is a one to one mappingof CPE-unique IDs to site IDs for this purpose. With the addition of theCloud Hub, a second CPE-unique ID is introduced that is mapped to thesame site ID (LWG instance) as the primary SMA client's CPE-unique ID.This is accomplished by leveraging the Device Registry service, whichmaintains a mapping of CPE ID and device type to site ID. The sessionserver of an embodiment, upon receipt of a UDP packet, looks up oridentifies the received packet's CPE-unique ID in the Gateway Registryand, if a corresponding site ID is found, routes the packet to theassociated LWG instance. If a corresponding site ID is not found, thesession server looks up the received CPE-unique ID with a general CloudHub device type ID and, if a corresponding site ID is found, routes thepacket to the associated LWG instance.

The LGW includes use of message tunneling over REST. The Cloud Hub, UDPand TCP messages coming from the CPE and received by the session serverare sent to the correct LWG via two REST endpoints. This enables thereceiving LWGW instance to run on a session server other than the one atwhich the message was received.

In an embodiment, when a UDP SMA message arrives at a session server, ifthe LWG corresponding to the CPE-unique ID message is not alreadyrunning on the given session server, then the session server starts anew LWG instance there, and if the corresponding LWGW is currentlyrunning on another session server, it will be gracefully shut down. Inthis way, the LWG is configured to move from one session server toanother.

In alternative embodiments, the security panel messages continue to usethe mechanism described herein (LWG migration), however, the Cloud Hubnetwork traffic employs a mechanism similar to that used by TunnelingCameras. More specifically:

1) Incoming UDP message to session server #1: session server #1 checksif LWG is running on session server #1.

-   -   If so, using a LocalRestClient, pass UDP message through to the        LWG via a rest endpoint that calls through to the        handleAsyncMessage method of the RIS device.    -   If not, check an LWG routing cache to see which session server        is hosting the LWG.    -   If a routing entry is found, use AMQPRestClient to pass the UDP        message through to the specific session server hosting the LWG        via the same rest endpoint that calls through to the        handleAsyncMessage method of the RIS device.    -   If no routing entry is found, or the session server returns 404        (e.g., stale routing entry), then the session server sends out a        broadcast request using the AMQPRestClient to ask all session        servers “who has this LWG”.    -   If a session server responds to the broadcast request, send the        async event to that session server as described herein.    -   If no session server responds to the broadcast request, start        the LWG on this session server (session server #1).        2) Incoming TCP message to session server #1: session server #1        checks if LWG is running on session server #1.    -   Use process described in 1 above to determine which session        server is hosting the LWG and pass the TCP message through        accordingly, but using a different rest endpoint than UDP        message handling. In the rest endpoint call, the name of the        session server with the TCP connection is sent along with the        request.    -   When the LWG receives TCP messages through the rest endpoint, it        keeps track of the name of the session server with the TCP        connection. The tunnel camera does this using a variable on the        camera device and the cloud hub device could do the same.        3) Sending a command from LWG over TCP connection.    -   When the LWG sends a command over the TCP connection, it sends a        command via the AMQPRestClient to the session server hosting the        TCP connection. It has this name saved from when it received the        first TCP message for the given connection.    -   If the TCP session server hostname is not known, or responds        with a 404 (e.g., TCP connection no longer there), then the LWG        sends out a broadcast request using the AMQPRestClient to ask        all session servers “who has this TCP connection”.    -   If a session server responds to the broadcast request, send the        command to that session server as described herein.    -   If no session server responds to the broadcast request, then the        LWG queues the command for a short time period (e.g., existing        RIS device functionality).

The CloudHub firmware update of an embodiment is accomplished over anHTTPS connection from the CloudHub to a secure server, to download anentire bundled CPE image. This single image includes the CloudHubupdatable firmware, including: OS image and drivers; SMA Client, whichincludes code for bootstrapping, AES-256 encryption, LED driver,firmware update logic, etc.; ezwLib Z-Wave stack.

A firmware update is initiated on the server by sending SMAv1 SystemCommand (command type 31) with Sub-Command “Upgrade Client Firmware”(system command type 3). This command simply provides a URL pointing tothe new firmware image. This will be an HTTPS URL for secure transfer ofthe image. When the Cloud Hub receives this command, it downloads theimage from a secure server via HTTPS, verifies a digest checksum, andflashes the new image.

Progress of the image download is communicated by the CloudHub bysending async event “Firmware upgrade % completed” (CPE Report Type 12);flashing progress is communicated by the CloudHub setting/clearingsystem status “Firmware Update Start” (Miscellaneous System Status 15).

Flashing a new firmware image does not factory-default the device, andexisting configuration, provisioning information, and encryption keysare retained. CloudHub of an embodiment is configured to use either adual-image scheme or re-flashing bootloader, so that a power-cycleduring image flashing will not brick CloudHub.

The SMA Client is configured to flash the Z-Wave chip firmware, whendirected to do so via SMAv1 System Command (command type 31) withSub-Command “Upgrade Client Firmware” (system command type 3),specifying a Z-Wave-specific filename.

SMAv1 security for tier-1 panel communication is enhanced by theout-of-band SMS channel from the server to the CPE. The cellular networkis a more restricted private network relative to a broadband network,and this is advantageous for re-keying the master key, when needed.Since CloudHub of an embodiment is configured as an always-on TCP/IPconnected device, another process is used in which a REST endpoint iscreated that uses an SMA set config command to “clear” the currentmaster key and restart. Upon restart, when the CPE discovers it has nomaster key, it performs the bootstrap as described herein to obtain anew master key.

The Lightweight Gateway (LWG) is a general term for the gateway statemachine that runs on the server, as described herein. There is also agateway state machine that runs in the home and this is commonlyreferred to as the iHub, although that code can run on other CPEhardware. The gateway state machine is configured to maintain track ofthe state of CPE devices such as security panels and cameras. Thegateway monitors and manages these devices, and also runs the rulesengine and exports the gateway core API which includes all endpointsthat begin with the prefix “/rest/[partner]/nw/[siteId]”.

The Lightweight Gateway is used for example when there is noconventional gateway in the home. In this configuration, devices likethe security panel and cameras talk directly to the server either usingthe cellular network or using the premises broadband network.

The Lightweight Gateway of an embodiment communicates with a variety ofsecurity panels and protocols. The security panels include the HoneywellQC3/Lynx and QC5/Touch, which use a proprietary RIS/ECP protocol(Honeywell). The security panels also include DSC SCW and PowerSeries,which use the iControl SMA V1 protocol. The LWG also communicates orintegrates with the 2 Gig Telular panel, which uses the iControl SMA V1protocol and supports ZWave devices like switches, dimmers, thermostatsand locks. In this configuration, the 2 Gig panel performs the role ofthe zwave device manager.

The LWG also communicates or integrates with the Honeywell TSS panel,which uses the iControl SMA V2 protocol and allows for complete remotepanel programming via SMA. The security panels to which the LWGcommunicates also include 3GUC panels, which use SMA V1 protocol and canconnect to SimonXT and other panels.

The LGW of an embodiment supports an XMPP Tunnel Camera (e.g.,OpenHome). This camera couples or connects to the server via broadbandusing the corresponding protocol tunneled over XMPP.

FIG. 4 is a block diagram showing communications of the LGW, under anembodiment. FIG. 5 is a block diagram showing an object model of theLGW, under an embodiment.

Regarding the system architecture, the LWG runs on a Session Server, asdescribed herein. The session server sits on the Web Tier, at the edgeof the data center. Other servers on the web tier include Apache serversand the Video Relay server, but are not so limited.

The LGW objects are hosted on the Session Server. They receive inboundcommunications from their corresponding security panel via the PanelService Provider (i.e. Honeywell). The inbound communication of anembodiment is UDP packets from a dedicated TCP/IP port. The outboundcommunications are packaged into binary SMS messages and delivered tothe security panel through third-party communication services, but arenot so limited.

The App Tier includes servers like the web portal and the gateway appserver. App tier servers have access to the persistence tier where theDatabase and NFS filesystem can be found.

The Web Tier of an embodiment does not have direct access to thepersistence tier, but is not so limited. As a result, for NFS andDatabase access, the LWG invokes APIs on the gateway app server. The LWGuses the REST API on the gateway app server as well as the legacyGwSessionService (gwsess.war). Most of these requests are made usinghttp, however, REST API requests can also be invoked using the AMQPtransport layer (AMQPRestClient) in which case these requests are routedthrough a work queue on the RabbitMQ Broker.

Regarding asynchronous architecture, a production session server of anembodiment includes 26 GB of memory, 2 CPUs, and is sized for 200K LWGs,but is not so limited. Each LWG uses approximately 100 KB of memory butis not so limited.

The LWGs running on a session server share the same virtual machine(e.g., Java), so the LWG code is configured to be high asynchronous soas to avoid blocking shared resources or using too many threads. Anembodiment includes shared network thread pools. These thread poolsdispatch tasks for handling incoming network activity (e.g., UDP and TCPmessage processing, API Requests, etc).

Embodiments include GlobalScheduler thread pools. In this configurationthere is a thread pool for non-blocking activity (tick pool), forexternal blocking requests (sync pool), and for camera operations(camera pool).

Because a large number of LWGs share the same memory, use is made of theStringCache when an object has a String member variable and that Stringis not likely to be unique. The StringCache is a shared lookup table ofcommonly used strings. When a code uses the StringCache then it has anint memory variable rather than a String, and this saves the LWG largeamounts of memory.

The Session server keeps track of all the LWGs it is running using the/data/ic/logs/session serialized files. Every time a new LWG is startedor stopped on the Session Server, these serialized files are updatedaccordingly. When the Session Server starts up after stopping (bothgracefully and ungracefully), these serialized files tell it which LWGsto start.

An LWG can move from one Session Server to another. The LWG of anembodiment is assigned to primary/secondary Session Server combination,but is not so limited. This is determined by the LWG group in which thesite resides. Each LWG group corresponds to a single primary SessionServer and a single secondary Session Server. The LWG group alsocorresponds to a dedicated port on the load balancer. This dedicatedport is configured to send all traffic to the primary Session Serverwhen it is up, and to the secondary Session Server if it is down(active/standby configuration). If traffic destined for a given LWGcomes in to a Session Server (either primary or secondary), the SessionServer will check if the LWG is already running on that server. If it isnot, then the Session Server will start the LWG and then pass to it thetraffic.

When a LWG starts up on a Session Server, it first sends aGatewayConnect request for the given LWG site to the Gateway App server.The same GatewayConnect request is also used when an iHub connects to aSession Server. The GatewayConnect request includes the hostname of theSession Server. The Gateway App server writes the Session Serverhostname to the database so that it knows to which Session Server agiven Gateway is connected. This is used for routing REST APIpassthrough requests, for example. When the Gateway app processes theGatewayConnect request, it checks which Session Server the given sitewas last connected to and, if its different from the new session server,then the Gateway App server sends a disconnect request to the lastsession server.

When a Session server receives a disconnect request for a given site, ifthe site is an iHub then the Session server will disconnect that iHub ifits still connected (it should not be). If the site is a LWG then thesession server will shut down that LWG gracefully, allowing the LWG toperform a final sync (sending any recent events to the database forpersistence) before removing the LWG from memory.

So, when a LWG starts up on a Session Server, the GatewayConnect requestensures that the LWG is no longer running on another Session Server. Ifthe load balancer decides that the primary Session Server for a givenport is down, it sends requests to the secondary Session Server. If theLWG is not already running on the secondary Session Server, thesecondary Session Server starts the LWG, ensuring that it is not runninganywhere else.

After the GatewayConnect request is completed, the LWG state machine isstarted up and it performs a “boot” Gateway sync. The “boot” GatewaySync is a request made to the Gateway app server for a completeconfiguration and state snapshot of the given site. The Gateway appserver reads the configuration and state from the DB and returns it tothe LWG. The LWG is then able to start up and resume the state andconfiguration that it had when last run.

Alternatively to the “boot” Gateway Sync, there is a startupoptimization that the LWG supports in which the contents of the “boot”Gateway Sync are written by the LWG to the NFS file system (using theGateway app server's GetResourceFile, PutResourceFile,DeleteResourceFile apis) when the LWG is shut down gracefully. When theLWG starts up, it will first check for this file before performing the“boot” Gateway Sync. If the file is found then the “boot” Gateway Syncis skipped.

An embodiment performs traffic routing via broker. The Session Serverincludes an instance of the REST Server Framework, which includes theAMQP work and broadcast queue support. The tunnel camera feature makesextensive use of AMQP Rest Client and Rest Server messaging forannouncing incoming camera connections, finding the Session Server witha given camera connected to it, sending camera requests and responsesacross different session servers (for example, when the Camera isconnected to a different session server from its LWG). The Rest APIendpoints are able to route requests to the LWG.

FIG. 6 is a block diagram of the application architecture, under anembodiment. Following are detailed descriptions of use case flowsteaching the interaction of elements of the application architecture.

FIG. 7 is a flow diagram for device state change, under an embodiment.This flow shows the signal and data flow that results when a devicestate changes.

-   -   1. iHub→Session Server    -   2. Session Server→Gateway Device State/Config    -   3. Gateway Device State/Config→DB    -   4. Gateway Device State/Config→Event Logging    -   5. Event Logging→DB    -   6. Event Logging→Broker (if user app is logged in to this site)

FIG. 8 is a flow diagram for media upload, under an embodiment. Thisflow shows the signal and data flow that results when media is uploadedto the server.

-   -   1. iHub→Camera    -   2. Camera→iHub/Registry Web    -   3. iHub/Registry Web→Media Upload    -   4. Media Upload→File System (local file system)    -   5. Media Upload→Broker    -   6. Broker→Media Upload (for processing)    -   7. Media Upload→File System (network file system)    -   8. Media Upload→Event Logging    -   9. Event Logging→DB    -   10. Event Logging→Broker (if user app is logged in to this site)

FIG. 9 is a flow diagram for live video, under an embodiment. This flowshows the signal and data flow that results when a client applicationsession accesses live video using the Relay Server.

-   -   1. Subscriber→Portal/Mobile/Admin Web (live video request)    -   2. Portal/Mobile/Admin Web→Customer Portal (live video request)    -   3. Customer Portal→Relay Server    -   4. Customer Portal→Gateway Device State/Config    -   5. Gateway Device State/Config→Session Server    -   6. Session Server→iHub    -   7. iHub→Camera    -   8. iHub→Relay Server    -   9. Customer Portal→Portal/Mobile/Admin Web (live video response)    -   10. Portal/Mobile/Admin Web→Subscriber (live video response)    -   11. Subscriber→Relay    -   12. Relay→iHub    -   13. iHub→Camera

FIG. 10 is a flow diagram for event trigger notification, under anembodiment. This flow shows the signal and data flow that results when adevice event triggers a notification to be sent to the customer.

-   -   1. iHub→Session Server    -   2. Session Server→Gateway Device State/Config    -   3. Gateway Device State/Config→DB    -   4. Gateway Device State/Config→Broker (if notification to be        sent)    -   5. Broker→Notification    -   6. Notification→DB    -   7. Notification→SMTP (if email notification)    -   8. Notification→Open Market (if SMS notification)

FIG. 11 is a flow diagram for activation iHub, under an embodiment. Thisflow shows the signal and data flow that results when an iHub or ngHubis activated.

-   -   1. Admin/Ops→Portal/Mobile/Admin Web (create site)    -   2. Portal/Mobile/Admin Web→Installer Portal (create site)    -   3. Installer Portal→DB (create site)    -   4. iHub→iHub/Registry Web (request: get cert)    -   5. iHub/Registry Web→Gateway Device State/Config (request: get        cert)    -   6. Gateway Device State/Config→DB (save cert)    -   7. Gateway Device State/Config→iHub/Registry Web (response: get        cert)    -   8. iHub/Registry Web→iHub (response: get cert)    -   9. iHub→Session Server    -   10. Session Server→Gateway Device State/Config (authenticate)    -   11. Gateway Device State/Config→DB    -   12. Installer Portal→DB (finalize site creation, set owner)

FIG. 12 is a flow diagram for activation LWG, under an embodiment. Thisflow shows the signal and data flow that results when a cellular-onlysecurity panel is activated.

-   -   1. Admin/Ops→Portal/Mobile/Admin Web (create site)    -   2. Portal/Mobile/Admin Web→Installer Portal (create site)    -   3. Installer Portal→DSC C24/Alarmnet (get SIM status)    -   4. Installer Portal→DB (create site)    -   5. Installer Portal→Session Server (start LWG)    -   6. Session Server→Lightweight Gateway (start LWG)    -   7. Installer Portal→Session Server (communication test)    -   8. Session Server→Lightweight Gateway (communication test)    -   9. Lightweight Gateway→SMS    -   10. SMS→SMPP    -   11. CPE Device→Session Server (UDP event)    -   12. Session Server→Lightweight Gateway    -   13. Lightweight Gateway→Gateway Device State/Config    -   14. Gateway Device State/Config→DB    -   15. Installer Portal→DB (finalize site creation, set owner)

FIG. 13 is a flow diagram for app sign-in (Web/Android app) iHub, underan embodiment. This flow shows the signal and data flow that resultswhen a customer (subscriber) with an iHub or ngHub signs in to theAndroid Application. The flow is largely the same for the Web Portal.

-   -   1. User→Portal/Mobile/Admin Web (authentication, get site        config)    -   2. Portal/Mobile/Admin Web→Mobile Portal (authentication, get        site config)    -   3. Mobile Portal→DB (authentication, get site config)    -   4. Mobile Portal→Broker (add event listener for site)    -   5. Mobile Portal→User (initial view data)    -   6. Mobile Portal→Session Server (client heartbeat)    -   7. Session Server→iHub (client heartbeat)    -   8. iHub→Session Server (sync)    -   9. Session Server→Gateway Device State/Config (sync)    -   10. Gateway Device State/Config→DB    -   11. Gateway Device State/Config→Broker (publish to listeners)    -   12. Broker→Mobile Portal (publish to listeners)    -   13. Mobile Portal→Portal/Mobile/Admin Web (update view data)    -   14. Portal/Mobile/Admin Web→User (update view data)

FIG. 14 is a flow diagram for app sign-in (Web/Android app) LWG, underan embodiment. This flow shows the signal and data flow that resultswhen a customer with a cellular-only panel (LWG) signs in to the AndroidApplication. The flow is largely the same for the Web Portal.

-   -   1. User→Portal/Mobile/Admin Web (authentication, get site        config)    -   2. Portal/Mobile/Admin Web→Mobile Portal (authentication, get        site config)    -   3. Mobile Portal→DB (authentication, get site config)    -   4. Mobile Portal→Broker (add event listener for site)    -   5. Mobile Portal→User (initial view data)    -   6. Mobile Portal→Session Server (client heartbeat)    -   7. Session Server→Lightweight Gateway (client heartbeat)    -   8. Lightweight Gateway→SMS (request TCP connection from panel)    -   9. SMS→SMPP    -   10. Lightweight Gateway→Session Server (sync)    -   11. Session Server→Gateway Device State/Config (sync)    -   12. Gateway Device State/Config→DB    -   13. Gateway Device State/Config→Broker (publish to listeners)    -   14. Broker→Mobile Portal (publish to listeners)    -   15. Mobile Portal→Portal/Mobile/Admin Web (update view data)    -   16. Portal/Mobile/Admin Web→User (update view data)

FIG. 15 is a flow diagram for app session, device event (Web/Androidapp), under an embodiment. This flow shows the signal and data flow thatresults when a customer is already signed in to the Android Applicationand a device event occurs. The flow is largely the same for the WebPortal.

-   -   1. Lightweight Gateway/iHub→Session Server (sync)    -   2. Session Server→Gateway Device State/Config (sync)    -   3. Gateway Device State/Config→DB    -   4. Gateway Device State/Config→Event Logging    -   5. Event Logging→DB    -   6. Event Logging→Broker (publish to listeners)    -   7. Broker→Mobile Portal (publish to listeners)    -   8. Mobile Portal→Portal/Mobile/Admin Web (update view data)    -   9. Portal/Mobile/Admin Web→User (update view data)

FIG. 16 is a flow diagram for app sign-in (iOS) iHub, under anembodiment. This flow shows the signal and data flow that results when acustomer with an iHub or ngHub signs in to the iOS Application.

-   -   1. User→Portal/Mobile/Admin Web (authentication, get site        config)    -   2. Portal/Mobile/Admin Web→Application Interface        (authentication, get site config)    -   3. Application Interface→DB (authentication, get site config)    -   4. Application Interface→Session Server (client heartbeat)    -   5. Session Server→iHub (client heartbeat)    -   6. User→Portal/Mobile/Admin Web (request: get current state,        deltas)    -   7. Portal/Mobile/Admin Web→Application Interface (request: get        current state, deltas)    -   8. Application Interface→Session Server (request: get current        state, deltas)    -   9. Session Server→iHub (request: get current state, deltas)    -   10. iHub→Session Server (response: get current state, deltas)    -   11. Session Server→Application Interface (response: get current        state, deltas)    -   12. Application Interface→Portal/Mobile/Admin Web (response: get        current state, deltas)    -   13. Portal/Mobile/Admin Web→User (response: get current state,        deltas)

FIG. 17 is a flow diagram for app sign-in (iOS) LWG, under anembodiment. This flow shows the signal and data flow that results when acustomer with a cellular-only panel (LWG) signs in to the iOSApplication.

-   -   1. User→Portal/Mobile/Admin Web (authentication, get site        config)    -   2. Portal/Mobile/Admin Web→Application Interface        (authentication, get site config)    -   3. Application Interface→DB (authentication, get site config)    -   4. Application Interface→Session Server (client heartbeat)    -   5. Session Server→Lightweight Gateway (client heartbeat)    -   6. Lightweight Gateway→SMS (request TCP connection from panel)    -   7. SMS→SMPP    -   8. User→Portal/Mobile/Admin Web (request: get current state,        deltas)    -   9. Portal/Mobile/Admin Web→Application Interface (request: get        current state, deltas)    -   10. Application Interface→Session Server (request: get current        state, deltas)    -   11. Session Server→Lightweight Gateway (request: get current        state, deltas)    -   12. Lightweight Gateway→Session Server (response: get current        state, deltas)    -   13. Session Server→Application Interface (response: get current        state, deltas)    -   14. Application Interface→Portal/Mobile/Admin Web (response: get        current state, deltas)    -   15. Portal/Mobile/Admin Web→User (response: get current state,        deltas)

FIG. 18 is a flow diagram for app session, device event (iOS app), underan embodiment. This flow shows the signal and data flow that resultswhen a customer is already signed in to the iOS Application and a deviceevent occurs.

-   -   1. User→Portal/Mobile/Admin Web (request: get current state,        deltas)    -   2. Portal/Mobile/Admin Web→Application Interface (request: get        current state, deltas)    -   3. Application Interface→Session Server (request: get current        state, deltas)    -   4. Session Server→iHub/Lightweight Gateway (request: get current        state, deltas)    -   5. iHub/Lightweight Gateway→Session Server (response: get        current state, deltas)    -   6. Session Server→Application Interface (response: get current        state, deltas)    -   7. Application Interface→Portal/Mobile/Admin Web (response: get        current state, deltas)    -   8. Portal/Mobile/Admin Web→User (response: get current state,        deltas)

FIG. 19 is a flow diagram for LWG remote arm, under an embodiment. Thisflow shows the signal and data flow that results when a LWG remotelyarms a cellular-only panel.

-   -   1. User→Portal/Mobile/Admin Web (request: arm panel)    -   2. Portal/Mobile/Admin Web→Application Interface (request: arm        panel)    -   3. Application Interface→Session Server (request: arm panel)    -   4. Session Server→Lightweight Gateway (request: arm panel)    -   5. Lightweight Gateway→CPE Device (send command over TCP        connection to device)    -   6. CPE Device→Session Server (UDP arm state change event)    -   7. Session Server→Lightweight Gateway (UDP arm state change        event)    -   8. Lightweight Gateway→Session Server (response: arm panel)    -   9. Session Server→Application Interface (response: arm panel)    -   10. Application Interface→Portal/Mobile/Admin Web (response: arm        panel)    -   11. Portal/Mobile/Admin Web→User (response: arm panel)

FIG. 20 is a flow diagram for iHub reboot, under an embodiment. Thisflow shows the signal and data flow that results when an iHub or ngHubreboots (includes references to the above flows).

-   -   1. iHub→iHub/Registry Web (request: get server info)    -   2. iHub/Registry Web→Gateway Registry (request: get server info)    -   3. Registry→DB (request: get server info)    -   4. Registry→iHub/Registry Web (response: get server info)    -   5. iHub/Registry Web→iHub (response: get server info)    -   6. iHub→iHub/Registry Web (request: get connect info)    -   7. iHub/Registry Web→Gateway Device State/Config (request: get        connect info)    -   8. Gateway Device State/Config→iHub/Registry Web (response: get        connect info)    -   9. iHub/Registry Web→iHub (response: get connect info)    -   10. iHub→Session Server    -   11. Session Server→Gateway Device State/Config (authenticate        request)    -   12. Gateway Device State/Config→DB    -   13. Gateway Device State/Config→Session Server (authenticate        response)

FIG. 21 is a flow diagram for iHub disconnect, under an embodiment. Thisflow shows the signal and data flow that results when an iHub or ngHubdisconnects from the server (includes references to the above flows).

-   -   1. Session Server→Gateway Device State/Config (disconnect)    -   2. Gateway Device State/Config→DB

The system of embodiments including the Cloud Hub and Virtual Gateway asdescribed in detail herein includes one or more components of the“integrated security system” described in detail herein and in theRelated Applications, which are incorporated by reference herein. Anexample of the “integrated security system” is available as one or moreof the numerous systems or platforms available from iControl Networks,Inc., Redwood City, Calif. The system of an embodiment described hereinincorporates one or more components of the “integrated security system”.The system of an embodiment described herein is coupled to one or morecomponents of the “integrated security system”. The system of anembodiment described herein integrates with one or more components ofthe “integrated security system”.

More particularly, the methods and processes of the integrated securitysystem, and hence the full functionality, can be implemented in thesystem described herein including the Cloud Hub and Virtual Gateway.Therefore, embodiments of the systems described herein integratebroadband and mobile access and control with conventional securitysystems and premise devices to provide a tri-mode security network(broadband, cellular/GSM, POTS access) that enables users to remotelystay connected to their premises. The integrated security system, whiledelivering remote premise monitoring and control functionality toconventional monitored premise protection, complements existing premiseprotection equipment. The integrated security system integrates into thepremise network and couples wirelessly with the conventional securitypanel, enabling broadband access to premise security systems. Automationdevices (cameras, lamp modules, thermostats, etc.) can be added,enabling users to remotely see live video and/or pictures and controlhome devices via their personal web portal or webpage, mobile phone,and/or other remote client device. Users can also receive notificationsvia email or text message when happenings occur, or do not occur, intheir home.

In accordance with the embodiments described herein, a wireless system(e.g., radio frequency (RF)) is provided that enables a securityprovider or consumer to extend the capabilities of an existingRF-capable security system or a non-RF-capable security system that hasbeen upgraded to support RF capabilities. The system includes anRF-capable Gateway device (physically located within RF range of theRF-capable security system) and associated software operating on theGateway device. The system also includes a web server, applicationserver, and remote database providing a persistent store for informationrelated to the system.

The security systems of an embodiment, referred to herein as theiControl security system or integrated security system, extend the valueof traditional home security by adding broadband access and theadvantages of remote home monitoring and home control through theformation of a security network including components of the integratedsecurity system integrated with a conventional premise security systemand a premise local area network (LAN). With the integrated securitysystem, conventional home security sensors, cameras, touchscreenkeypads, lighting controls, and/or Internet Protocol (IP) devices in thehome (or business) become connected devices that are accessible anywherein the world from a web browser, mobile phone or through content-enabledtouchscreens. The integrated security system experience allows securityoperators to both extend the value proposition of their monitoredsecurity systems and reach new consumers that include broadband usersinterested in staying connected to their family, home and property whenthey are away from home.

The integrated security system of an embodiment includes securityservers (also referred to herein as iConnect servers or security networkservers) and an iHub gateway (also referred to herein as the gateway,the iHub, or the iHub client) that couples or integrates into a homenetwork (e.g., LAN) and communicates directly with the home securitypanel, in both wired and wireless installations. The security system ofan embodiment automatically discovers the security system components(e.g., sensors, etc.) belonging to the security system and connected toa control panel of the security system and provides consumers with fulltwo-way access via web and mobile portals. The gateway supports variouswireless protocols and can interconnect with a wide range of controlpanels offered by security system providers. Service providers and userscan then extend the system's capabilities with the additional IPcameras, lighting modules or security devices such as interactivetouchscreen keypads. The integrated security system adds an enhancedvalue to these security systems by enabling consumers to stay connectedthrough email and SMS alerts, photo push, event-based video capture andrule-based monitoring and notifications. This solution extends the reachof home security to households with broadband access.

The integrated security system builds upon the foundation afforded bytraditional security systems by layering broadband and mobile access, IPcameras, interactive touchscreens, and an open approach to homeautomation on top of traditional security system configurations. Theintegrated security system is easily installed and managed by thesecurity operator, and simplifies the traditional security installationprocess, as described below.

The integrated security system provides an open systems solution to thehome security market. As such, the foundation of the integrated securitysystem customer premises equipment (CPE) approach has been to abstractdevices, and allows applications to manipulate and manage multipledevices from any vendor. The integrated security system DeviceConnecttechnology that enables this capability supports protocols, devices, andpanels from GE Security and Honeywell, as well as consumer devices usingZ-Wave, IP cameras (e.g., Ethernet, wifi, and Homeplug), and IPtouchscreens. The DeviceConnect is a device abstraction layer thatenables any device or protocol layer to interoperate with integratedsecurity system components. This architecture enables the addition ofnew devices supporting any of these interfaces, as well as add entirelynew protocols.

The benefit of DeviceConnect is that it provides supplier flexibility.The same consistent touchscreen, web, and mobile user experience operateunchanged on whatever security equipment selected by a security systemprovider, with the system provider's choice of IP cameras, backend datacenter and central station software.

The integrated security system provides a complete system thatintegrates or layers on top of a conventional host security systemavailable from a security system provider. The security system providertherefore can select different components or configurations to offer(e.g., CDMA, GPRS, no cellular, etc.) as well as have iControl modifythe integrated security system configuration for the system provider'sspecific needs (e.g., change the functionality of the web or mobileportal, add a GE or Honeywell-compatible TouchScreen, etc.).

The integrated security system integrates with the security systemprovider infrastructure for central station reporting directly viaBroadband and GPRS alarm transmissions. Traditional dial-up reporting issupported via the standard panel connectivity. Additionally, theintegrated security system provides interfaces for advancedfunctionality to the CMS, including enhanced alarm events, systeminstallation optimizations, system test verification, videoverification, 2-way voice over IP and GSM.

The integrated security system is an IP centric system that includesbroadband connectivity so that the gateway augments the existingsecurity system with broadband and GPRS connectivity. If broadband isdown or unavailable GPRS may be used, for example. The integratedsecurity system supports GPRS connectivity using an optional wirelesspackage that includes a GPRS modem in the gateway. The integratedsecurity system treats the GPRS connection as a higher cost thoughflexible option for data transfers. In an embodiment the GPRS connectionis only used to route alarm events (e.g., for cost), however the gatewaycan be configured (e.g., through the iConnect server interface) to actas a primary channel and pass any or all events over GPRS. Consequently,the integrated security system does not interfere with the current plainold telephone service (POTS) security panel interface. Alarm events canstill be routed through POTS; however the gateway also allows suchevents to be routed through a broadband or GPRS connection as well. Theintegrated security system provides a web application interface to theCSR tool suite as well as XML, web services interfaces for programmaticintegration between the security system provider's existing call centerproducts. The integrated security system includes, for example, APIsthat allow the security system provider to integrate components of theintegrated security system into a custom call center interface. The APIsinclude XML web service APIs for integration of existing security systemprovider call center applications with the integrated security systemservice. All functionality available in the CSR Web application isprovided with these API sets. The Java and XML-based APIs of theintegrated security system support provisioning, billing, systemadministration, CSR, central station, portal user interfaces, andcontent management functions, to name a few. The integrated securitysystem can provide a customized interface to the security systemprovider's billing system, or alternatively can provide security systemdevelopers with APIs and support in the integration effort.

The integrated security system provides or includes business componentinterfaces for provisioning, administration, and customer care to name afew. Standard templates and examples are provided with a definedcustomer professional services engagement to help integrate OSS/BSSsystems of a Service Provider with the integrated security system.

The integrated security system components support and allow for theintegration of customer account creation and deletion with a securitysystem. The iConnect APIs provides access to the provisioning andaccount management system in iConnect and provide full support foraccount creation, provisioning, and deletion. Depending on therequirements of the security system provider, the iConnect APIs can beused to completely customize any aspect of the integrated securitysystem backend operational system.

The integrated security system includes a gateway that supports thefollowing standards-based interfaces, to name a few: Ethernet IPcommunications via Ethernet ports on the gateway, and standardXML/TCP/IP protocols and ports are employed over secured SSL sessions;USB 2.0 via ports on the gateway; 802.11b/g/n IP communications;GSM/GPRS RF WAN communications; CDMA 1×RTT RF WAN communications(optional, can also support EVDO and 3G technologies).

The gateway supports the following proprietary interfaces, to name afew: interfaces including Dialog RF network (319.5 MHz) and RS485Superbus 2000 wired interface; RF mesh network (908 MHz); and interfacesincluding RF network (345 MHz) and RS485/RS232bus wired interfaces.

Regarding security for the IP communications (e.g., authentication,authorization, encryption, anti-spoofing, etc), the integrated securitysystem uses SSL to encrypt all IP traffic, using server andclient-certificates for authentication, as well as authentication in thedata sent over the SSL-encrypted channel. For encryption, integratedsecurity system issues public/private key pairs at the time/place ofmanufacture, and certificates are not stored in any online storage in anembodiment.

The integrated security system does not need any special rules at thecustomer premise and/or at the security system provider central stationbecause the integrated security system makes outgoing connections usingTCP over the standard HTTP and HTTPS ports. Provided outbound TCPconnections are allowed then no special requirements on the firewallsare necessary.

FIG. 22 is a block diagram of the integrated security system 100, underan embodiment. The integrated security system 100 of an embodimentincludes the gateway 102 and the security servers 104 coupled to theconventional home security system 110. At a customer's home or business,the gateway 102 connects and manages the diverse variety of homesecurity and self-monitoring devices. The gateway 102 communicates withthe iConnect Servers 104 located in the service provider's data center106 (or hosted in integrated security system data center), with thecommunication taking place via a communication network 108 or othernetwork (e.g., cellular network, internet, etc.). These servers 104manage the system integrations necessary to deliver the integratedsystem service described herein. The combination of the gateway 102 andthe iConnect servers 104 enable a wide variety of remote client devices120 (e.g., PCs, mobile phones and PDAs) allowing users to remotely stayin touch with their home, business and family. In addition, thetechnology allows home security and self-monitoring information, as wellas relevant third party content such as traffic and weather, to bepresented in intuitive ways within the home, such as on advancedtouchscreen keypads.

The integrated security system service (also referred to as iControlservice) can be managed by a service provider via browser-basedMaintenance and Service Management applications that are provided withthe iConnect Servers. Or, if desired, the service can be more tightlyintegrated with existing OSS/BSS and service delivery systems via theiConnect web services-based XML APIs.

The integrated security system service can also coordinate the sendingof alarms to the home security Central Monitoring Station (CMS) 199.Alarms are passed to the CMS 199 using standard protocols such asContact ID or SIA and can be generated from the home security panellocation as well as by iConnect server 104 conditions (such as lack ofcommunications with the integrated security system). In addition, thelink between the security servers 104 and CMS 199 provides tighterintegration between home security and self-monitoring devices and thegateway 102. Such integration enables advanced security capabilitiessuch as the ability for CMS personnel to view photos taken at the time aburglary alarm was triggered. For maximum security, the gateway 102 andiConnect servers 104 support the use of a mobile network (both GPRS andCDMA options are available) as a backup to the primary broadbandconnection.

The integrated security system service is delivered by hosted serversrunning software components that communicate with a variety of clienttypes while interacting with other systems. FIG. 23 is a block diagramof components of the integrated security system 100, under anembodiment. Following is a more detailed description of the components.

The iConnect servers 104 support a diverse collection of clients 120ranging from mobile devices, to PCs, to in-home security devices, to aservice provider's internal systems. Most clients 120 are used byend-users, but there are also a number of clients 120 that are used tooperate the service.

Clients 120 used by end-users of the integrated security system 100include, but are not limited to, the following:

-   -   Clients based on gateway client applications 202 (e.g., a        processor-based device running the gateway technology that        manages home security and automation devices).    -   A web browser 204 accessing a Web Portal application, performing        end-user configuration and customization of the integrated        security system service as well as monitoring of in-home device        status, viewing photos and video, etc. Device and user        management can also be performed by this portal application.    -   A mobile device 206 (e.g., PDA, mobile phone, etc.) accessing        the integrated security system Mobile Portal. This type of        client 206 is used by end-users to view system status and        perform operations on devices (e.g., turning on a lamp, arming a        security panel, etc.) rather than for system configuration tasks        such as adding a new device or user.    -   PC or browser-based “widget” containers 208 that present        integrated security system service content, as well as other        third-party content, in simple, targeted ways (e.g. a widget        that resides on a PC desktop and shows live video from a single        in-home camera). “Widget” as used herein means applications or        programs in the system.    -   Touchscreen home security keypads 208 and advanced in-home        devices that present a variety of content widgets via an        intuitive touchscreen user interface.    -   Notification recipients 210 (e.g., cell phones that receive        SMS-based notifications when certain events occur (or don't        occur), email clients that receive an email message with similar        information, etc.).    -   Custom-built clients (not shown) that access the iConnect web        services XML API to interact with users' home security and        self-monitoring information in new and unique ways. Such clients        could include new types of mobile devices, or complex        applications where integrated security system content is        integrated into a broader set of application features.

In addition to the end-user clients, the iConnect servers 104 support PCbrowser-based Service Management clients that manage the ongoingoperation of the overall service. These clients run applications thathandle tasks such as provisioning, service monitoring, customer supportand reporting.

There are numerous types of server components of the iConnect servers104 of an embodiment including, but not limited to, the following:Business Components which manage information about all of the homesecurity and self-monitoring devices; End-User Application Componentswhich display that information for users and access the BusinessComponents via published XML APIs; and Service Management ApplicationComponents which enable operators to administer the service (thesecomponents also access the Business Components via the XML APIs, andalso via published SNMP MIBs).

The server components provide access to, and management of, the objectsassociated with an integrated security system installation. Thetop-level object is the “network.” It is a location where a gateway 102is located, and is also commonly referred to as a site or premises; thepremises can include any type of structure (e.g., home, office,warehouse, etc.) at which a gateway 102 is located. Users can onlyaccess the networks to which they have been granted permission. Within anetwork, every object monitored by the gateway 102 is called a device.Devices include the sensors, cameras, home security panels andautomation devices, as well as the controller or processor-based devicerunning the gateway applications.

Various types of interactions are possible between the objects in asystem. Automations define actions that occur as a result of a change instate of a device. For example, take a picture with the front entrycamera when the front door sensor changes to “open”. Notifications aremessages sent to users to indicate that something has occurred, such asthe front door going to “open” state, or has not occurred (referred toas an iWatch notification). Schedules define changes in device statesthat are to take place at predefined days and times. For example, setthe security panel to “Armed” mode every weeknight at 11:00 pm.

The iConnect Business Components are responsible for orchestrating allof the low-level service management activities for the integratedsecurity system service. They define all of the users and devicesassociated with a network (site), analyze how the devices interact, andtrigger associated actions (such as sending notifications to users). Allchanges in device states are monitored and logged. The BusinessComponents also manage all interactions with external systems asrequired, including sending alarms and other related self-monitoringdata to the home security Central Monitoring System (CMS) 199. TheBusiness Components are implemented as portable Java J2EE Servlets, butare not so limited.

The following iConnect Business Components manage the main elements ofthe integrated security system service, but the embodiment is not solimited:

-   -   A Registry Manager 220 defines and manages users and networks.        This component is responsible for the creation, modification and        termination of users and networks. It is also where a user's        access to networks is defined.    -   A Network Manager 222 defines and manages security and        self-monitoring devices that are deployed on a network (site).        This component handles the creation, modification, deletion and        configuration of the devices, as well as the creation of        automations, schedules and notification rules associated with        those devices.    -   A Data Manager 224 manages access to current and logged state        data for an existing network and its devices. This component        specifically does not provide any access to network management        capabilities, such as adding new devices to a network, which are        handled exclusively by the Network Manager 222.    -   To achieve optimal performance for all types of queries, data        for current device states is stored separately from historical        state data (a.k.a. “logs”) in the database. A Log Data Manager        226 performs ongoing transfers of current device state data to        the historical data log tables.

Additional iConnect Business Components handle direct communicationswith certain clients and other systems, for example:

-   -   An iHub Manager 228 directly manages all communications with        gateway clients, including receiving information about device        state changes, changing the configuration of devices, and        pushing new versions of the gateway client to the hardware it is        running on.    -   A Notification Manager 230 is responsible for sending all        notifications to clients via SMS (mobile phone messages), email        (via a relay server like an SMTP email server), etc.    -   An Alarm and CMS Manager 232 sends critical server-generated        alarm events to the home security Central Monitoring Station        (CMS) and manages all other communications of integrated        security system service data to and from the CMS.    -   The Element Management System (EMS) 234 is an iControl Business        Component that manages all activities associated with service        installation, scaling and monitoring, and filters and packages        service operations data for use by service management        applications. The SNMP MIBs published by the EMS can also be        incorporated into any third party monitoring system if desired.

The iConnect Business Components store information about the objectsthat they manage in the iControl Service Database 240 and in theiControl Content Store 242. The iControl Content Store is used to storemedia objects like video, photos and widget content, while the ServiceDatabase stores information about users, networks, and devices. Databaseinteraction is performed via a JDBC interface. For security purposes,the Business Components manage all data storage and retrieval.

The iControl Business Components provide web services-based APIs thatapplication components use to access the Business Components'capabilities. Functions of application components include presentingintegrated security system service data to end-users, performingadministrative duties, and integrating with external systems andback-office applications.

The primary published APIs for the iConnect Business Components include,but are not limited to, the following:

-   -   A Registry Manager API 252 provides access to the Registry        Manager Business Component's functionality, allowing management        of networks and users.    -   A Network Manager API 254 provides access to the Network Manager        Business Component's functionality, allowing management of        devices on a network.    -   A Data Manager API 256 provides access to the Data Manager        Business Component's functionality, such as setting and        retrieving (current and historical) data about device states.    -   A Provisioning API 258 provides a simple way to create new        networks and configure initial default properties.

Each API of an embodiment includes two modes of access: Java API or XMLAPI. The XML APIs are published as web services so that they can beeasily accessed by applications or servers over a network. The Java APIsare a programmer-friendly wrapper for the XML APIs. Applicationcomponents and integrations written in Java should generally use theJava APIs rather than the XML APIs directly.

The iConnect Business Components also have an XML-based interface 260for quickly adding support for new devices to the integrated securitysystem. This interface 260, referred to as DeviceConnect 260, is aflexible, standards-based mechanism for defining the properties of newdevices and how they can be managed. Although the format is flexibleenough to allow the addition of any type of future device, pre-definedXML profiles are currently available for adding common types of devicessuch as sensors (SensorConnect), home security panels (PanelConnect) andIP cameras (CameraConnect).

The iConnect End-User Application Components deliver the user interfacesthat run on the different types of clients supported by the integratedsecurity system service. The components are written in portable JavaJ2EE technology (e.g., as Java Servlets, as JavaServer Pages (JSPs),etc.) and they all interact with the iControl Business Components viathe published APIs.

The following End-User Application Components generate CSS-basedHTML/JavaScript that is displayed on the target client. Theseapplications can be dynamically branded with partner-specific logos andURL links (such as Customer Support, etc.). The End-User ApplicationComponents of an embodiment include, but are not limited to, thefollowing:

-   -   An iControl Activation Application 270 that delivers the first        application that a user sees when they set up the integrated        security system service. This wizard-based web browser        application securely associates a new user with a purchased        gateway and the other devices included with it as a kit (if        any). It primarily uses functionality published by the        Provisioning API.    -   An iControl Web Portal Application 272 runs on PC browsers and        delivers the web-based interface to the integrated security        system service. This application allows users to manage their        networks (e.g. add devices and create automations) as well as to        view/change device states, and manage pictures and videos.        Because of the wide scope of capabilities of this application,        it uses three different Business Component APIs that include the        Registry Manager API, Network Manager API, and Data Manager API,        but the embodiment is not so limited.    -   An iControl Mobile Portal 274 is a small-footprint web-based        interface that runs on mobile phones and PDAs. This interface is        optimized for remote viewing of device states and        pictures/videos rather than network management. As such, its        interaction with the Business Components is primarily via the        Data Manager API.    -   Custom portals and targeted client applications can be provided        that leverage the same Business Component APIs used by the above        applications.    -   A Content Manager Application Component 276 delivers content to        a variety of clients. It sends multimedia-rich user interface        components to widget container clients (both PC and        browser-based), as well as to advanced touchscreen keypad        clients. In addition to providing content directly to end-user        devices, the Content Manager 276 provides widget-based user        interface components to satisfy requests from other Application        Components such as the iControl Web 272 and Mobile 274 portals.

A number of Application Components are responsible for overallmanagement of the service. These pre-defined applications, referred toas Service Management Application Components, are configured to offeroff-the-shelf solutions for production management of the integratedsecurity system service including provisioning, overall servicemonitoring, customer support, and reporting, for example. The ServiceManagement Application Components of an embodiment include, but are notlimited to, the following:

-   -   A Service Management Application 280 allows service        administrators to perform activities associated with service        installation, scaling and monitoring/alerting. This application        interacts heavily with the Element Management System (EMS)        Business Component to execute its functionality, and also        retrieves its monitoring data from that component via protocols        such as SNMP MIBs.    -   A Kitting Application 282 is used by employees performing        service provisioning tasks. This application allows home        security and self-monitoring devices to be associated with        gateways during the warehouse kitting process.    -   A CSR Application and Report Generator 284 is used by personnel        supporting the integrated security system service, such as CSRs        resolving end-user issues and employees enquiring about overall        service usage. Pushes of new gateway firmware to deployed        gateways is also managed by this application.

The iConnect servers 104 also support custom-built integrations with aservice provider's existing OSS/BSS, CSR and service delivery systems290. Such systems can access the iConnect web services XML API totransfer data to and from the iConnect servers 104. These types ofintegrations can compliment or replace the PC browser-based ServiceManagement applications, depending on service provider needs.

As described above, the integrated security system of an embodimentincludes a gateway, or iHub. The gateway of an embodiment includes adevice that is deployed in the home or business and couples or connectsthe various third-party cameras, home security panels, sensors anddevices to the iConnect server over a WAN connection as described indetail herein. The gateway couples to the home network and communicatesdirectly with the home security panel in both wired and wireless sensorinstallations. The gateway is configured to be low-cost, reliable andthin so that it complements the integrated security system network-basedarchitecture.

The gateway supports various wireless protocols and can interconnectwith a wide range of home security control panels. Service providers andusers can then extend the system's capabilities by adding IP cameras,lighting modules and additional security devices. The gateway isconfigurable to be integrated into many consumer appliances, includingset-top boxes, routers and security panels. The small and efficientfootprint of the gateway enables this portability and versatility,thereby simplifying and reducing the overall cost of the deployment.

FIG. 24 is a block diagram of the gateway 102 including gateway softwareor applications, under an embodiment. The gateway software architectureis relatively thin and efficient, thereby simplifying its integrationinto other consumer appliances such as set-top boxes, routers, touchscreens and security panels. The software architecture also provides ahigh degree of security against unauthorized access. This sectiondescribes the various key components of the gateway softwarearchitecture.

The gateway application layer 302 is the main program that orchestratesthe operations performed by the gateway. The Security Engine 304provides robust protection against intentional and unintentionalintrusion into the integrated security system network from the outsideworld (both from inside the premises as well as from the WAN). TheSecurity Engine 304 of an embodiment comprises one or more sub-modulesor components that perform functions including, but not limited to, thefollowing:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the gateway and iConnect        server in order to prevent unauthorized spoofing and attacks.        Data sent from the iConnect server to the gateway application        (or vice versa) is digitally signed as an additional layer of        security. Digital signing provides both authentication and        validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The gateway provides for 128-bit        SSL encapsulation of the user picture and video data sent over        the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A gateway-enabled device is assigned a unique activation key for        activation with an iConnect server. This ensures that only valid        gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying gateway-enabled devices        have the knowledge that only a gateway with the correct serial        number and activation key can be activated for use with an        iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 allows for seamless and secureupdates to the gateway firmware through the iControl MaintenanceApplication on the server 104, providing a transparent, hassle-freemechanism for the service provider to deploy new features and bug fixesto the installed user base. The firmware download mechanism is tolerantof connection loss, power interruption and user interventions (bothintentional and unintentional). Such robustness reduces down time andcustomer support issues. Gateway firmware can be remotely downloadeither for one gateway at a time, a group of gateways, or in batches.

The Automations engine 308 manages the user-defined rules of interactionbetween the different devices (e.g. when door opens turn on the light).Though the automation rules are programmed and reside at theportal/server level, they are cached at the gateway level in order toprovide short latency between device triggers and actions.

DeviceConnect 310 includes definitions of all supported devices (e.g.,cameras, security panels, sensors, etc.) using a standardized plug-inarchitecture. The DeviceConnect module 310 offers an interface that canbe used to quickly add support for any new device as well as enablinginteroperability between devices that use differenttechnologies/protocols. For common device types, pre-defined sub-moduleshave been defined, making supporting new devices of these types eveneasier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 is responsible for executing the user definedschedules (e.g., take a picture every five minutes; every day at 8 amset temperature to 65 degrees Fahrenheit, etc.). Though the schedulesare programmed and reside at the iConnect server level they are sent tothe scheduler within the gateway application. The Schedules Engine 318then interfaces with SensorConnect 312 to ensure that scheduled eventsoccur at precisely the desired time.

The Device Management module 320 is in charge of all discovery,installation and configuration of both wired and wireless IP devices(e.g., cameras, etc.) coupled or connected to the system. Networked IPdevices, such as those used in the integrated security system, requireuser configuration of many IP and security parameters—to simplify theuser experience and reduce the customer support burden, the devicemanagement module of an embodiment handles the details of thisconfiguration. The device management module also manages the videorouting module described below.

The video routing engine 322 is responsible for delivering seamlessvideo streams to the user with zero-configuration. Through a multi-step,staged approach the video routing engine uses a combination of UPnPport-forwarding, relay server routing and STUN/TURN peer-to-peerrouting.

FIG. 25 is a block diagram of components of the gateway 102, under anembodiment. Depending on the specific set of functionality desired bythe service provider deploying the integrated security system service,the gateway 102 can use any of a number of processors 402, due to thesmall footprint of the gateway application firmware. In an embodiment,the gateway could include the Broadcom BCM5354 as the processor forexample. In addition, the gateway 102 includes memory (e.g., FLASH 404,RAM 406, etc.) and any number of input/output (I/O) ports 408.

Referring to the WAN portion 410 of the gateway 102, the gateway 102 ofan embodiment can communicate with the iConnect server using a number ofcommunication types and/or protocols, for example Broadband 412, GPRS414 and/or Public Switched Telephone Network (PTSN) 416 to name a few.In general, broadband communication 412 is the primary means ofconnection between the gateway 102 and the iConnect server 104 and theGPRS/CDMA 414 and/or PSTN 416 interfaces acts as backup for faulttolerance in case the user's broadband connection fails for whateverreason, but the embodiment is not so limited.

Referring to the LAN portion 420 of the gateway 102, various protocolsand physical transceivers can be used to communicate to off-the-shelfsensors and cameras. The gateway 102 is protocol-agnostic andtechnology-agnostic and as such can easily support almost any devicenetworking protocol. The gateway 102 can, for example, support GE andHoneywell security RF protocols 422, Z-Wave 424, serial (RS232 andRS485) 426 for direct connection to security panels as well as WiFi 428(802.11b/g) for communication to WiFi cameras.

The integrated security system includes couplings or connections among avariety of IP devices or components, and the device management module isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system of an embodiment uses a “sandbox” network todiscover and manage all IP devices coupled or connected as components ofthe system. The IP devices of an embodiment include wired devices,wireless devices, cameras, interactive touchscreens, and security panelsto name a few. These devices can be wired via ethernet cable or Wifidevices, all of which are secured within the sandbox network, asdescribed below. The “sandbox” network is described in detail below.

FIG. 26 is a block diagram 500 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255-257 are coupled to the gateway 102 using a securenetwork coupling or connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption). Thenetwork coupling or connection between the gateway 102 and the networkdevices 255-257 is a private coupling or connection in that it issegregated from any other network couplings or connections. The gateway102 is coupled to the premise router/firewall 252 via a coupling with apremise LAN 250. The premise router/firewall 252 is coupled to abroadband modem 251, and the broadband modem 251 is coupled to a WAN 200or other network outside the premise. The gateway 102 thus enables orforms a separate wireless network, or sub-network, that includes somenumber of devices and is coupled or connected to the LAN 250 of the hostpremises. The gateway sub-network can include, but is not limited to,any number of other devices like WiFi IP cameras, security panels (e.g.,IP-enabled), and security touchscreens, to name a few. The gateway 102manages or controls the sub-network separately from the LAN 250 andtransfers data and information between components of the sub-network andthe LAN 250/WAN 200, but is not so limited. Additionally, other networkdevices 254 can be coupled to the LAN 250 without being coupled to thegateway 102.

FIG. 27 is a block diagram 600 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255-257 are coupled to the gateway 102. The networkcoupling or connection between the gateway 102 and the network devices255-257 is a private coupling or connection in that it is segregatedfrom any other network couplings or connections. The gateway 102 iscoupled or connected between the premise router/firewall 252 and thebroadband modem 251. The broadband modem 251 is coupled to a WAN 200 orother network outside the premise, while the premise router/firewall 252is coupled to a premise LAN 250. As a result of its location between thebroadband modem 251 and the premise router/firewall 252, the gateway 102can be configured or function as the premise router routing specifieddata between the outside network (e.g., WAN 200) and the premiserouter/firewall 252 of the LAN 250. As described above, the gateway 102in this configuration enables or forms a separate wireless network, orsub-network, that includes the network or premise devices 255-257 and iscoupled or connected between the LAN 250 of the host premises and theWAN 200. The gateway sub-network can include, but is not limited to, anynumber of network or premise devices 255-257 like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The gateway 102 manages or controls the sub-network separately fromthe LAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the gateway 102.

The examples described above with reference to FIGS. 5 and 6 arepresented only as examples of IP device integration. The integratedsecurity system is not limited to the type, number and/or combination ofIP devices shown and described in these examples, and any type, numberand/or combination of IP devices is contemplated within the scope ofthis disclosure as capable of being integrated with the premise network.

The integrated security system of an embodiment includes a touchscreen(also referred to as the iControl touchscreen or integrated securitysystem touchscreen), as described above, which provides core securitykeypad functionality, content management and presentation, and embeddedsystems design. The networked security touchscreen system of anembodiment enables a consumer or security provider to easily andautomatically install, configure and manage the security system andtouchscreen located at a customer premise. Using this system thecustomer may access and control the local security system, local IPdevices such as cameras, local sensors and control devices (such aslighting controls or pipe freeze sensors), as well as the local securitysystem panel and associated security sensors (such as door/window,motion, and smoke detectors). The customer premise may be a home,business, and/or other location equipped with a wired or wirelessbroadband IP connection.

The system of an embodiment includes a touchscreen with a configurablesoftware user interface and/or a gateway device (e.g., iHub) thatcouples or connects to a premise security panel through a wired orwireless connection, and a remote server that provides access to contentand information from the premises devices to a user when they are remotefrom the home. The touchscreen supports broadband and/or WAN wirelessconnectivity. In this embodiment, the touchscreen incorporates an IPbroadband connection (e.g., Wifi radio, Ethernet port, etc.), and/or acellular radio (e.g., GPRS/GSM, CDMA, WiMax, etc.). The touchscreendescribed herein can be used as one or more of a security systeminterface panel and a network user interface (UI) that provides aninterface to interact with a network (e.g., LAN, WAN, internet, etc.).

The touchscreen of an embodiment provides an integrated touchscreen andsecurity panel as an all-in-one device. Once integrated using thetouchscreen, the touchscreen and a security panel of a premise securitysystem become physically co-located in one device, and the functionalityof both may even be co-resident on the same CPU and memory (though thisis not required).

The touchscreen of an embodiment also provides an integrated IP videoand touchscreen UI. As such, the touchscreen supports one or morestandard video CODECs/players (e.g., H.264, Flash Video, MOV, MPEG4,M-JPEG, etc.). The touchscreen UI then provides a mechanism (such as acamera or video widget) to play video. In an embodiment the video isstreamed live from an IP video camera. In other embodiments the videocomprises video clips or photos sent from an IP camera or from a remotelocation.

The touchscreen of an embodiment provides a configurable user interfacesystem that includes a configuration supporting use as a securitytouchscreen. In this embodiment, the touchscreen utilizes a modular userinterface that allows components to be modified easily by a serviceprovider, an installer, or even the end user. Examples of such a modularapproach include using Flash widgets, HTML-based widgets, or otherdownloadable code modules such that the user interface of thetouchscreen can be updated and modified while the application isrunning. In an embodiment the touchscreen user interface modules can bedownloaded over the internet. For example, a new security configurationwidget can be downloaded from a standard web server, and the touchscreenthen loads such configuration app into memory, and inserts it in placeof the old security configuration widget. The touchscreen of anembodiment is configured to provide a self-install user interface.

Embodiments of the networked security touchscreen system describedherein include a touchscreen device with a user interface that includesa security toolbar providing one or more functions including arm,disarm, panic, medic, and alert. The touchscreen therefore includes atleast one screen having a separate region of the screen dedicated to asecurity toolbar. The security toolbar of an embodiment is present inthe dedicated region at all times that the screen is active.

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing home-basedfunctions. The home-based functions of an embodiment include managing,viewing, and/or controlling IP video cameras. In this embodiment,regions of the home screen are allocated in the form of widget icons;these widget icons (e.g. for cameras, thermostats, lighting, etc)provide functionality for managing home systems. So, for example, adisplayed camera icon, when selected, launches a Camera Widget, and theCamera widget in turn provides access to video from one or more cameras,as well as providing the user with relevant camera controls (take apicture, focus the camera, etc.)

The touchscreen of an embodiment includes a home screen having aseparate region of the screen allocated to managing, viewing, and/orcontrolling internet-based content or applications. For example, theWidget Manager UI presents a region of the home screen (up to andincluding the entire home screen) where internet widgets icons such asweather, sports, etc. may be accessed). Each of these icons may beselected to launch their respective content services.

The touchscreen of an embodiment is integrated into a premise networkusing the gateway, as described above. The gateway as described hereinfunctions to enable a separate wireless network, or sub-network, that iscoupled, connected, or integrated with another network (e.g., WAN, LANof the host premises, etc.). The sub-network enabled by the gatewayoptimizes the installation process for IP devices, like the touchscreen,that couple or connect to the sub-network by segregating these IPdevices from other such devices on the network. This segregation of theIP devices of the sub-network further enables separate security andprivacy policies to be implemented for these IP devices so that, wherethe IP devices are dedicated to specific functions (e.g., security), thesecurity and privacy policies can be tailored specifically for thespecific functions. Furthermore, the gateway and the sub-network itforms enables the segregation of data traffic, resulting in faster andmore efficient data flow between components of the host network,components of the sub-network, and between components of the sub-networkand components of the network.

The touchscreen of an embodiment includes a core functional embeddedsystem that includes an embedded operating system, required hardwaredrivers, and an open system interface to name a few. The core functionalembedded system can be provided by or as a component of a conventionalsecurity system (e.g., security system available from GE Security).These core functional units are used with components of the integratedsecurity system as described herein. Note that portions of thetouchscreen description below may include reference to a host premisesecurity system (e.g., GE security system), but these references areincluded only as an example and do not limit the touchscreen tointegration with any particular security system.

As an example, regarding the core functional embedded system, a reducedmemory footprint version of embedded Linux forms the core operatingsystem in an embodiment, and provides basic TCP/IP stack and memorymanagement functions, along with a basic set of low-level graphicsprimitives. A set of device drivers is also provided or included thatoffer low-level hardware and network interfaces. In addition to thestandard drivers, an interface to the RS 485 bus is included thatcouples or connects to the security system panel (e.g., GE Concordpanel). The interface may, for example, implement the Superbus 2000protocol, which can then be utilized by the more comprehensivetransaction-level security functions implemented in PanelConnecttechnology (e.g SetAlarmLevel (int level, int partition, char*accessCode)). Power control drivers are also provided.

FIG. 28 is a block diagram of a touchscreen 700 of the integratedsecurity system, under an embodiment. The touchscreen 700 generallyincludes an application/presentation layer 702 with a residentapplication 704, and a core engine 706. The touchscreen 700 alsoincludes one or more of the following, but is not so limited:applications of premium services 710, widgets 712, a caching proxy 714,network security 716, network interface 718, security object 720,applications supporting devices 722, PanelConnect API 724, a gatewayinterface 726, and one or more ports 728.

More specifically, the touchscreen, when configured as a home securitydevice, includes but is not limited to the following application orsoftware modules: RS 485 and/or RS-232 bus security protocols toconventional home security system panel (e.g., GE Concord panel);functional home security classes and interfaces (e.g. Panel ARM state,Sensor status, etc.); Application/Presentation layer or engine; ResidentApplication; Consumer Home Security Application; installer home securityapplication; core engine; and System bootloader/Software Updater. Thecore Application engine and system bootloader can also be used tosupport other advanced content and applications. This provides aseamless interaction between the premise security application and otheroptional services such as weather widgets or IP cameras.

An alternative configuration of the touchscreen includes a firstApplication engine for premise security and a second Application enginefor all other applications. The integrated security system applicationengine supports content standards such as HTML, XML, Flash, etc. andenables a rich consumer experience for all ‘widgets’, whethersecurity-based or not. The touchscreen thus provides service providersthe ability to use web content creation and management tools to buildand download any ‘widgets’ regardless of their functionality.

As discussed above, although the Security Applications have specificlow-level functional requirements in order to interface with the premisesecurity system, these applications make use of the same fundamentalapplication facilities as any other ‘widget’, application facilitiesthat include graphical layout, interactivity, application handoff,screen management, and network interfaces, to name a few.

Content management in the touchscreen provides the ability to leverageconventional web development tools, performance optimized for anembedded system, service provider control of accessible content, contentreliability in a consumer device, and consistency between ‘widgets’ andseamless widget operational environment. In an embodiment of theintegrated security system, widgets are created by web developers andhosted on the integrated security system Content Manager (and stored inthe Content Store database). In this embodiment the server componentcaches the widgets and offers them to consumers through the web-basedintegrated security system provisioning system. The servers interactwith the advanced touchscreen using HTTPS interfaces controlled by thecore engine and dynamically download widgets and updates as needed to becached on the touchscreen. In other embodiments widgets can be accesseddirectly over a network such as the Internet without needing to gothrough the iControl Content Manager

Referring to FIG. 28 , the touchscreen system is built on a tieredarchitecture, with defined interfaces between theApplication/Presentation Layer (the Application Engine) on the top, theCore Engine in the middle, and the security panel and gateway APIs atthe lower level. The architecture is configured to provide maximumflexibility and ease of maintenance.

The application engine of the touchscreen provides the presentation andinteractivity capabilities for all applications (widgets) that run onthe touchscreen, including both core security function widgets and thirdparty content widgets. FIG. 29 is an example screenshot 800 of anetworked security touchscreen, under an embodiment. This examplescreenshot 800 includes three interfaces or user interface (UI)components 802-806, but is not so limited. A first UI 802 of thetouchscreen includes icons by which a user controls or accessesfunctions and/or components of the security system (e.g., “Main”,“Panic”, “Medic”, “Fire”, state of the premise alarm system (e.g.,disarmed, armed, etc.), etc.); the first UI 802, which is also referredto herein as a security interface, is always presented on thetouchscreen. A second UI 804 of the touchscreen includes icons by whicha user selects or interacts with services and other network content(e.g., clock, calendar, weather, stocks, news, sports, photos, maps,music, etc.) that is accessible via the touchscreen. The second UI 804is also referred to herein as a network interface or content interface.A third UI 806 of the touchscreen includes icons by which a user selectsor interacts with additional services or componets (e.g., intercomcontrol, security, cameras coupled to the system in particular regions(e.g., front door, baby, etc.) available via the touchscreen.

A component of the application engine is the Presentation Engine, whichincludes a set of libraries that implement the standards-based widgetcontent (e.g., XML, HTML, JavaScript, Flash) layout and interactivity.This engine provides the widget with interfaces to dynamically load bothgraphics and application logic from third parties, support high leveldata description language as well as standard graphic formats. The setof web content-based functionality available to a widget developer isextended by specific touchscreen functions implemented as local webservices by the Core Engine.

The resident application of the touchscreen is the master service thatcontrols the interaction of all widgets in the system, and enforces thebusiness and security rules required by the service provider. Forexample, the resident application determines the priority of widgets,thereby enabling a home security widget to override resource requestsfrom a less critical widget (e.g. a weather widget). The residentapplication also monitors widget behavior, and responds to client orserver requests for cache updates.

The core engine of the touchscreen manages interaction with othercomponents of the integrated security system, and provides an interfacethrough which the resident application and authorized widgets can getinformation about the home security system, set alarms, install sensors,etc. At the lower level, the Core Engine's main interactions are throughthe PanelConnect API, which handles all communication with the securitypanel, and the gateway Interface, which handles communication with thegateway. In an embodiment, both the iHub Interface and PanelConnect APIare resident and operating on the touchscreen. In another embodiment,the PanelConnect API runs on the gateway or other device that providessecurity system interaction and is accessed by the touchscreen through aweb services interface.

The Core Engine also handles application and service level persistentand cached memory functions, as well as the dynamic provisioning ofcontent and widgets, including but not limited to: flash memorymanagement, local widget and content caching, widget version management(download, cache flush new/old content versions), as well as the cachingand synchronization of user preferences. As a portion of these servicesthe Core engine incorporates the bootloader functionality that isresponsible for maintaining a consistent software image on thetouchscreen, and acts as the client agent for all software updates. Thebootloader is configured to ensure full update redundancy so thatunsuccessful downloads cannot corrupt the integrated security system.

Video management is provided as a set of web services by the CoreEngine. Video management includes the retrieval and playback of localvideo feeds as well as remote control and management of cameras (allthrough iControl CameraConnect technology).

Both the high level application layer and the mid-level core engine ofthe touchscreen can make calls to the network. Any call to the networkmade by the application layer is automatically handed off to a localcaching proxy, which determines whether the request should be handledlocally. Many of the requests from the application layer are webservices API requests, although such requests could be satisfied by theiControl servers, they are handled directly by the touchscreen and thegateway. Requests that get through the caching proxy are checked againsta white list of acceptable sites, and, if they match, are sent offthrough the network interface to the gateway. Included in the NetworkSubsystem is a set of network services including HTTP, HTTPS, andserver-level authentication functions to manage the secure client-serverinterface. Storage and management of certificates is incorporated as apart of the network services layer.

Server components of the integrated security system servers supportinteractive content services on the touchscreen. These server componentsinclude, but are not limited to the content manager, registry manager,network manager, and global registry, each of which is described herein.

The Content Manager oversees aspects of handling widget data and rawcontent on the touchscreen. Once created and validated by the serviceprovider, widgets are ‘ingested’ to the Content Manager, and then becomeavailable as downloadable services through the integrated securitysystem Content Management APIs. The Content manager maintains versionsand timestamp information, and connects to the raw data contained in thebackend Content Store database. When a widget is updated (or new contentbecomes available) all clients registering interest in a widget aresystematically updated as needed (a process that can be configured at anaccount, locale, or system-wide level).

The Registry Manager handles user data, and provisioning accounts,including information about widgets the user has decided to install, andthe user preferences for these widgets.

The Network Manager handles getting and setting state for all devices onthe integrated security system network (e.g., sensors, panels, cameras,etc.). The Network manager synchronizes with the gateway, the advancedtouchscreen, and the subscriber database.

The Global Registry is a primary starting point server for all clientservices, and is a logical referral service that abstracts specificserver locations/addresses from clients (touchscreen, gateway 102,desktop widgets, etc.). This approach enables easy scaling/migration ofserver farms.

The touchscreen of an embodiment operates wirelessly with a premisesecurity system. The touchscreen of an embodiment incorporates an RFtransceiver component that either communicates directly with the sensorsand/or security panel over the panel's proprietary RF frequency, or thetouchscreen communicates wirelessly to the gateway over 802.11,Ethernet, or other IP-based communications channel, as described indetail herein. In the latter case the gateway implements thePanelConnect interface and communicates directly to the security paneland/or sensors over wireless or wired networks as described in detailabove.

The touchscreen of an embodiment is configured to operate with multiplesecurity systems through the use of an abstracted security systeminterface. In this embodiment, the PanelConnect API can be configured tosupport a plurality of proprietary security system interfaces, eithersimultaneously or individually as described herein. In one embodiment ofthis approach, the touchscreen incorporates multiple physical interfacesto security panels (e.g. GE Security RS-485, Honeywell RF, etc.) inaddition to the PanelConnect API implemented to support multiplesecurity interfaces. The change needed to support this in PanelConnectis a configuration parameter specifying the panel type connection thatis being utilized.

So for example, the setARMState( ) function is called with an additionalparameter (e.g., Armstate=setARMState(type=“ARM STAY|ARM AWAY|DISARM”,Parameters=“ExitDelay=30|Lights=OFF”, panelType=“GE Concord4 RS485”)).The ‘panelType’ parameter is used by the setARMState function (and inpractice by all of the PanelConnect functions) to select an algorithmappropriate to the specific panel out of a plurality of alogorithms.

The touchscreen of an embodiment is self-installable. Consequently, thetouchscreen provides a ‘wizard’ approach similar to that used intraditional computer installations (e.g. InstallShield). The wizard canbe resident on the touchscreen, accessible through a web interface, orboth. In one embodiment of a touchscreen self-installation process, theservice provider can associate devices (sensors, touchscreens, securitypanels, lighting controls, etc.) remotely using a web-basedadministrator interface.

The touchscreen of an embodiment includes a battery backup system for asecurity touchscreen. The touchscreen incorporates a standard Li-ion orother battery and charging circuitry to allow continued operation in theevent of a power outage. In an embodiment the battery is physicallylocated and connected within the touchscreen enclosure. In anotherembodiment the battery is located as a part of the power transformer, orin between the power transformer and the touchscreen.

The example configurations of the integrated security system describedabove with reference to FIGS. 5 and 6 include a gateway that is aseparate device, and the touchscreen couples to the gateway. However, inan alternative embodiment, the gateway device and its functionality canbe incorporated into the touchscreen so that the device managementmodule, which is now a component of or included in the touchscreen, isin charge of the discovery, installation and configuration of the IPdevices coupled or connected to the system, as described above. Theintegrated security system with the integrated touchscreen/gateway usesthe same “sandbox” network to discover and manage all IP devices coupledor connected as components of the system.

The touchscreen of this alternative embodiment integrates the componentsof the gateway with the components of the touchscreen as describedherein. More specifically, the touchscreen of this alternativeembodiment includes software or applications described above withreference to FIG. 3 . In this alternative embodiment, the touchscreenincludes the gateway application layer 302 as the main program thatorchestrates the operations performed by the gateway. A Security Engine304 of the touchscreen provides robust protection against intentionaland unintentional intrusion into the integrated security system networkfrom the outside world (both from inside the premises as well as fromthe WAN). The Security Engine 304 of an embodiment comprises one or moresub-modules or components that perform functions including, but notlimited to, the following:

-   -   Encryption including 128-bit SSL encryption for gateway and        iConnect server communication to protect user data privacy and        provide secure communication.    -   Bi-directional authentication between the touchscreen and        iConnect server in order to prevent unauthorized spoofing and        attacks. Data sent from the iConnect server to the gateway        application (or vice versa) is digitally signed as an additional        layer of security. Digital signing provides both authentication        and validation that the data has not been altered in transit.    -   Camera SSL encapsulation because picture and video traffic        offered by off-the-shelf networked IP cameras is not secure when        traveling over the Internet. The touchscreen provides for        128-bit SSL encapsulation of the user picture and video data        sent over the internet for complete user security and privacy.    -   802.11b/g/n with WPA-2 security to ensure that wireless camera        communications always takes place using the strongest available        protection.    -   A touchscreen-enabled device is assigned a unique activation key        for activation with an iConnect server. This ensures that only        valid gateway-enabled devices can be activated for use with the        specific instance of iConnect server in use. Attempts to        activate gateway-enabled devices by brute force are detected by        the Security Engine. Partners deploying touchscreen-enabled        devices have the knowledge that only a gateway with the correct        serial number and activation key can be activated for use with        an iConnect server. Stolen devices, devices attempting to        masquerade as gateway-enabled devices, and malicious outsiders        (or insiders as knowledgeable but nefarious customers) cannot        effect other customers' gateway-enabled devices.

As standards evolve, and new encryption and authentication methods areproven to be useful, and older mechanisms proven to be breakable, thesecurity manager can be upgraded “over the air” to provide new andbetter security for communications between the iConnect server and thegateway application, and locally at the premises to remove any risk ofeavesdropping on camera communications.

A Remote Firmware Download module 306 of the touchscreen allows forseamless and secure updates to the gateway firmware through the iControlMaintenance Application on the server 104, providing a transparent,hassle-free mechanism for the service provider to deploy new featuresand bug fixes to the installed user base. The firmware downloadmechanism is tolerant of connection loss, power interruption and userinterventions (both intentional and unintentional). Such robustnessreduces down time and customer support issues. Touchscreen firmware canbe remotely download either for one touchscreen at a time, a group oftouchscreen, or in batches.

The Automations engine 308 of the touchscreen manages the user-definedrules of interaction between the different devices (e.g. when door opensturn on the light). Though the automation rules are programmed andreside at the portal/server level, they are cached at the gateway levelin order to provide short latency between device triggers and actions.

DeviceConnect 310 of the touchscreen touchscreen includes definitions ofall supported devices (e.g., cameras, security panels, sensors, etc.)using a standardized plug-in architecture. The DeviceConnect module 310offers an interface that can be used to quickly add support for any newdevice as well as enabling interoperability between devices that usedifferent technologies/protocols. For common device types, pre-definedsub-modules have been defined, making supporting new devices of thesetypes even easier. SensorConnect 312 is provided for adding new sensors,CameraConnect 316 for adding IP cameras, and PanelConnect 314 for addinghome security panels.

The Schedules engine 318 of the touchscreen is responsible for executingthe user defined schedules (e.g., take a picture every five minutes;every day at 8 am set temperature to 65 degrees Fahrenheit, etc.).Though the schedules are programmed and reside at the iConnect serverlevel they are sent to the scheduler within the gateway application ofthe touchscreen. The Schedules Engine 318 then interfaces withSensorConnect 312 to ensure that scheduled events occur at precisely thedesired time.

The Device Management module 320 of the touchscreen is in charge of alldiscovery, installation and configuration of both wired and wireless IPdevices (e.g., cameras, etc.) coupled or connected to the system.Networked IP devices, such as those used in the integrated securitysystem, require user configuration of many IP and security parameters,and the device management module of an embodiment handles the details ofthis configuration. The device management module also manages the videorouting module described below.

The video routing engine 322 of the touchscreen is responsible fordelivering seamless video streams to the user with zero-configuration.Through a multi-step, staged approach the video routing engine uses acombination of UPnP port-forwarding, relay server routing and STUN/TURNpeer-to-peer routing. The video routing engine is described in detail inthe Related Applications.

FIG. 30 is a block diagram 900 of network or premise device integrationwith a premise network 250, under an embodiment. In an embodiment,network devices 255, 256, 957 are coupled to the touchscreen 902 using asecure network connection such as SSL over an encrypted 802.11 link(utilizing for example WPA-2 security for the wireless encryption), andthe touchscreen 902 coupled to the premise router/firewall 252 via acoupling with a premise LAN 250. The premise router/firewall 252 iscoupled to a broadband modem 251, and the broadband modem 251 is coupledto a WAN 200 or other network outside the premise. The touchscreen 902thus enables or forms a separate wireless network, or sub-network, thatincludes some number of devices and is coupled or connected to the LAN250 of the host premises. The touchscreen sub-network can include, butis not limited to, any number of other devices like WiFi IP cameras,security panels (e.g., IP-enabled), and IP devices, to name a few. Thetouchscreen 902 manages or controls the sub-network separately from theLAN 250 and transfers data and information between components of thesub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the touchscreen 902.

FIG. 31 is a block diagram 1000 of network or premise device integrationwith a premise network 250, under an alternative embodiment. The networkor premise devices 255, 256, 1057 are coupled to the touchscreen 1002,and the touchscreen 1002 is coupled or connected between the premiserouter/firewall 252 and the broadband modem 251. The broadband modem 251is coupled to a WAN 200 or other network outside the premise, while thepremise router/firewall 252 is coupled to a premise LAN 250. As a resultof its location between the broadband modem 251 and the premiserouter/firewall 252, the touchscreen 1002 can be configured or functionas the premise router routing specified data between the outside network(e.g., WAN 200) and the premise router/firewall 252 of the LAN 250. Asdescribed above, the touchscreen 1002 in this configuration enables orforms a separate wireless network, or sub-network, that includes thenetwork or premise devices 255, 156, 1057 and is coupled or connectedbetween the LAN 250 of the host premises and the WAN 200. Thetouchscreen sub-network can include, but is not limited to, any numberof network or premise devices 255, 256, 1057 like WiFi IP cameras,security panels (e.g., IP-enabled), and security touchscreens, to name afew. The touchscreen 1002 manages or controls the sub-network separatelyfrom the LAN 250 and transfers data and information between componentsof the sub-network and the LAN 250/WAN 200, but is not so limited.Additionally, other network devices 254 can be coupled to the LAN 250without being coupled to the touchscreen 1002.

The gateway of an embodiment, whether a stand-along component orintegrated with a touchscreen, enables couplings or connections and thusthe flow or integration of information between various components of thehost premises and various types and/or combinations of IP devices, wherethe components of the host premises include a network (e.g., LAN) and/ora security system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

The gateway of an embodiment, as described herein, enables couplings orconnections and thus the flow of information between various componentsof the host premises and various types and/or combinations of IPdevices, where the components of the host premises include a network, asecurity system or subsystem to name a few. Consequently, the gatewaycontrols the association between and the flow of information or databetween the components of the host premises. For example, the gateway ofan embodiment forms a sub-network coupled to another network (e.g., WAN,LAN, etc.), with the sub-network including IP devices. The gatewayfurther enables the association of the IP devices of the sub-networkwith appropriate systems on the premises (e.g., security system, etc.).Therefore, for example, the gateway can form a sub-network of IP devicesconfigured for security functions, and associate the sub-network onlywith the premises security system, thereby segregating the IP devicesdedicated to security from other IP devices that may be coupled toanother network on the premises.

The system of an embodiment including the Cloud Hub and Virtual Gatewayas described in detail herein includes one or more components of the“integrated cloud system (ICS)” described in detail herein. The systemof an embodiment described herein incorporates one or more components ofthe “ICS”. The system of an embodiment described herein is coupled toone or more components of the “ICS”. The system of an embodimentdescribed herein integrates with one or more components of the “ICS”.

FIG. 32 is a block diagram of the integrated cloud system or platform,under an embodiment. The integrated cloud system (ICS) of an embodimentcomprises cloud-based components that include a Cloud IntegrationService/Server (CIS) coupled to a system server (e.g., “IcontrolServer”, also referred to herein as the service provider server) via aninternal event bus. The CIS, system server, and event bus areimplemented by the service provider in data centers of the serviceprovider's customers, but are not so limited.

The system server is coupled to customer-premises equipment (CPE) atcorresponding subscriber premises of numerous subscribers. The CPEincludes one or more of security panels, security systems, gateways,hubs, touchscreens, and Wi-Fi access points that operate as a gateway tothe system servers and ICS. The CPE is described in detail in theRelated Applications incorporated by reference herein.

The CIS is coupled to a partner's production server (“partner server”)via a Cloud Integration Adapter (CIA). The partner server interacts withtheir products/services that their users wish to integrate into theirICS platform. The Cloud Integration Adapter provides the system serverand CIS with REST endpoints to call for checking the health of theadapter, associating with adapter cloud devices, and processing eventscoming from the CIS. Furthermore, the Cloud Integration Adapter isresponsible for sending events to the CIS as acknowledgement of incomingsystem events, and as an endpoint for Adapter managed cloud deviceevents to be reported into the system servers.

The ICS of an embodiment effects integration of cloud services andinternet-connected devices with the user interface, Rules Engine andother components and functions of the service provider system. Thisintegration enables third party and/or other connected devices (e.g.,smart door bells (e.g, Doorbot, etc.), door locks, garage door operators(e.g., Chamberlain, etc.), cameras (e.g., Dropcam, etc.), thermostats(e.g., Nest, etc.), lighting systems (e.g., Philips Hue, etc.), lightingdevices, lawn irrigation systems (e.g., Rachio, etc.), plant sensors,pet feeders, weather stations, rain sensors, pool controls, air qualitysensors, music systems, remote controllers, internet user interfaces,connected systems, connected vehicles, etc.), and third party services(e.g weather forecasting services and applications (e.g., Accuweather,etc.), family networking services and applications, partner or thirdparty services, Accuweather, MSO digital assets such as voicemail,etc.), to control or trigger automations in the service provider systemusing the user interface, Rules Engine and other components andfunctions of the service provider system. This enables end-users tointegrate and use their previously-standalone internet-connected deviceswith each other as well as with their service provider-based service.

The ICS of an embodiment as described in detail herein includes one ormore components of the “integrated security system” described in detailin the Related Applications, which are incorporated by reference herein.An example of the “integrated security system” is available as one ormore of the numerous systems or platforms available from iControlNetworks, Inc., Redwood City, Calif. The ICS of an embodimentincorporates one or more components of the “integrated security system”.The ICS of an embodiment is coupled to one or more components of the“integrated security system”. The ICS of an embodiment integrates withone or more components of the “integrated security system”.

The system server includes or hosts a partner proxy and an integrationREST application programming interface (API). The integration REST APIis coupled to the CIS. The partner proxy is coupled to a correspondingpartner server, and is also coupled to a Card UI (“REST Client”). Thepartner proxy is configured to proxy API calls from the Partner's CardUI (REST client) to the Partner Server and appends the appropriate OAuthToken for a given user. This enables all client UIs to be enabled aftera single OAuth pairing is completed (i.e., if one user authorizesPartner's product, all users and clients on the same account will haveit auto-enabled and populated). This also improves security by notstoring the user's credentials on the Partner's server in the client UI.The Card UI of an example embodiment is an HTML5-based user interfacecard developed by the Partner, or service provider, that is embeddedinto the service provider user interface (e.g., mobile app, web portal).

The ICS of an embodiment includes Cloud Actions and Triggers (CAT),which enable third party connected devices and services to triggerautomations in the service provider system, thereby enabling end-usersto integrate and use their previously-standalone internet connecteddevices with their service provider-based service.

Devices and services that are hosted outside of the automation platformor network are referred to as ‘cloud objects’ and provide numerous usecases when integrated with the system of an embodiment. The descriptionthat follows includes details of aspects of the system including but notlimited to server infrastructure required to support external cloudobjects, data format definitions for actions and triggers across theevent bus, the process of onboarding external cloud objects, integrationof cloud objects with the CPE rules engine, common OAuth2 Support forCloud Services, and card UI/SDK Support for Cloud Objects.

The CAT of an embodiment integrates partner services into the ICSplatform including support for rules on the CPE and partner-specificuser interfaces based on the Card UI. The system of an embodimentincludes a web API for the CIS for which partners develop IntegrationAdapters (also referred to as “adapters”) responsible for thetranslation of service provider events and operations into partnerproprietary calls. Partners also develop Cards with the Card SDK inorder to get branded partner specific user interfaces. The partners ofan embodiment host their Integration Adapters in their environments,however in an alternative embodiment the adapters are hosed by the ICSdescribed herein.

While the rules engine of an embodiment is included and running on CPE,the embodiments herein are not so limited. In an alternative embodimentthe rules engine is included and running on a system server or othercomponent of the ICS platform.

In another alternative embodiment the rules engine is distributedbetween the CPE and ICS platform so that a set of rules is included andrunning on the CPE while another set of rules is included and running onthe ICS platform. For example, rules controlling actions and triggerslimited to local devices in the premises, and not using any data orinformation from a device or service outside the premises, are includedand running on the CPE. Likewise, rules controlling actions and triggersinvolving device(s) in the premises, and also involving device(s) orservice(s) outside the premises, are included and running on the CPE.

The CAT includes but is not limited to use cases comprising ServiceAssociation, Cloud Object Creation, Service Disassociation, Cloud ObjectSynchronization, Card UI Interactions, Rule Authoring, and RuleExecution. Each of the use cases is described in detail herein.

Upon startup, the Partner's Cloud Integration Adapter uses username,password and partnerKey to authenticate with the CIS. The username,password and partnerKey are provided by the service provider. ThePartner's Event Callback URL and Health Check URL are defined initiallyas part of the partner onboarding process. The CIS provides two URLs forthe partner to optionally update the two URLs at runtime.

The Register Event callback URI allows partner to update the EventCallback URL at runtime.

-   -   /cloudIntegration/[partnerName]/eventCallback/registerEventCallback?partner        Endpoint    -   Url=[partnerUrl]        Descripti    -   Update the eventCallback URL for a partner    -   on    -   Method POST        -   x-login—username of the integration user    -   Header x-password—password of the integration user        -   x-partnerKey—unique key issued by Service provider to the            partner    -   URL partnerName: The unique name of the partner provided by        Service provider paramete    -   rs partnerUrl: The updated Event Callback URL    -   Result HTTP response 200 if successful

An example payload includes but is not limited to the following:

  curl -k -L -v -H “X-login: <username>” -H “X-password: test” -H“x-partnerKey: key” - X POST“https://<server>/cloudIntegration/icontrol/cloudIntegrations/rachio/eventCallback/registerEventCallback?partnerUrl=https://rachioAdapter/updatedEventCallbackUrl”

The Register Health Check Callback URI allows partner to update theHealth Check URL at runtime.

Endpo/cloudIntegration/[partnerName]/healthCheckCallback/registerHealthCheckCallb

-   -   int ack?partnerHealthCheckUrl=[partnerHealthCheckUrl]        Descri    -   Update healthCheckCallback URL for partner        ption        Metho    -   POST    -   d        -   x-login—username of the integration userx-password—password            of the    -   Heade        -   integration userx-partnerKey—A unique key issued by Service            provider to the    -   r        -   partner    -   URL        -   partnerName: The unique name of the partnerpartner    -   param        -   HealthCheckUrl: The updated health check URL    -   eters    -   Result HTTP response 200 if successful

An example payload includes but is not limited to the following:

  curl -k -L -v -H “Content-Type: text/xml ” -H “X-login: <username>” -H“X-password: test” -H “x-partnerKey: key” -X POSThttps://<server>/cloudIntegration/icontrol/cloudIntegrations/rachio/healthCheckCallback/registerHealthCheckCallback?partnerHealthCheckUrl=https://rachioAdapter/updatedHealthcheckcallback.

For both the Event Callback Registration and Health Check CallbackRegistration, the CIS responds with a HTTP 200 if the POST is accepted.Appropriate HTTP error code will be returned for error conditions.

The Health Check Callback service implemented by the Partner supportsHTTP GET operations, and responds with HTTP 200 to indicate all systemsare functioning properly. Any other response will be considered anindication that the adapter is not available. The CIS of an embodimentperiodically checks availability of the Integration Adapter, and theperiodicity is configurable.

The cloud integration user lifecycle of an embodiment embodies the coreuser experiences from a technical viewpoint (i.e., technical use cases).The following user lifecycle use cases are described in detail herein:Service Association (User Onboarding); Updating new userproduct(s)/service(s) on the Partner's server; Product/Service statusupdates; Controlling user's product(s)/service(s) from the serviceprovider platform; User Offboarding of one or moreproduct(s)/service(s).

Service Association (User Onboarding) is initiated by the user via aservice provider user interface when the user selects a Partner devicetype from the list of devices available to pair to the user's Serviceprovider system. FIG. 33 is a flow diagram for Service Association,under an embodiment. Service Association (Partner Onboarding) isinitiated by a Card UI of an embodiment when the user selects a partnerfrom a partner list. The list of all possible partners and their custom(partner specific) cards are built into each release of the Card UI(they are not dynamically downloaded from a server). However the list ofenabled partners (and related metadata) is dynamically retrieved fromService provider server via an API.

Once the user selects a partner service for association, three-leggedOAuth2 begins. A browser control is created, has its context populatedwith information identifying the user, and calls Service provider OAUTHRedirect servlet, which in turn opens the OAuth2 landing page URL withthe required parameters (response_type, client_id and token). This page,served by the partner's web server, collects the user's ID and passwordand successfully authenticates.

After the user is authenticated, the partner server issues an HTTP 302redirect to the Service provider OAuth Callback servlet located in theportal server and includes an authorization code as well as the rest ofthe original browser context. The OAuth Callback servlet contacts thepartner's service to exchange the authorization code for an access tokenwhich it stores in the database.

Then, the OAuth Callback servlet will call the ‘Associate Account URL’provided by the partner. The access token for the user account isattached to the request as the Authorization header to identify theuser. The response to the call will include the user's account id in thepartner system and a list of cloud devices owned by the user. Aftersuccessful account association, HTTP 200 is returned to the browserindicating the completion of the service association process.

The service provider OAUTH callback URL has the following format, but isnot so limited: https://<servername>/oauth/oauthPartner/<partnerName>.It is recommended that a service provider deployment registers this URLin the partner's system. As an alternate (less secure) option, this URLcan be passed to the partner system as a parameter in the first leg ofthe OAUTH process.

The system of an embodiment includes Cloud Object Synchronization asdescribed herein. After a service has been associated for auser/account, the system server has the list of cloud devices owned bythe user. If the user adds/removes a device in the partner's system,partner server calls the Service provider Cloud Integration Service APIto inform Service provider regarding the change. Conversely, if userremoves a cloud device association in Service provider Card UI, an eventwill be sent to the partner's system via the ‘Event Callback URL’.

After completing user authentication, the OAuth token for the useraccount is attached to a request to associate the account (AssociateAccount in FIG. 2 ). The Partner Server's response to the call willinclude the user's Account ID in the Partner's system and a list ofcloud-enabled devices owned by the user in that account. Aftersuccessful account association, HTTP 200 is returned to the browserindicating the completion of the service association process. After aservice has been associated for a user/account, the Service providerserver will have the list of cloud devices owned by the user.

Account association with the CIS is the process by which the systemserver creates the relationship between the Service provider user andpartner cloud devices. The Cloud Integration Service sends, via HTTPPOST, a JSON Object containing the OAuth Access Token.

An example Associate Account Request follows but the embodiment is notso limited:

URL The ‘Associate Account URL’ provided by the partner in the CloudIntegration Submission Form. Description Get the user's account/deviceinfo from the partner. Method POST Header Authorization - ‘Bearer xxxxx’where xxxxx is the user's access token. URL customerName: The name ofthe Service provider server. parameters

When an account association request is received by the Cloud IntegrationAdapter, it responds with a JSON message in the following format:

  Associate Account Response {  “virtualDevice.siteId”:“acc_1234”, “virtualDevice.instanceIds”:[   {    “id”:“device-inst001”,   “name”:“Front Sprinkler”   },   {    “id”:“device-inst002”,   “name”:“Backyard Sprinkler”   }  ] }Where:

Field Name Description virtualDevice.siteId The user ID in the Partner'ssystem. This will be the global identifier used by Service provider torefer to the Partner's primary user. virtualDevice.instanceIds A list(JSON Array) of devices the Partner or user wishes Service provider tointeract with. id The Device ID in the Partner's system. name A friendlydisplay name for this device.

A HTTP 200 is expected along with this data. Error codes should includean HTTP 500 for errors, and an HTTP 401 for improper OAuth token.

Updating status of partner product (events) involves user's interactingwith the Partner's product/service through a Partner client (e.g.,Partner mobile app) or the user may interact with the device locally andchange its state, mode, or otherwise affect the product/service'sstatus. Events received from the Partner's Cloud Integration Adapter canbe treated as a trigger for a rule in the Service provider system (e.g.,when the backyard sprinkler system is running, lock the pet door).

An example payload description follows but the embodiment is not solimited:

-   -   Endp        -   /cloudIntegration/[partnerName]/events/submitCloudEvent    -   oint    -   Descr        -   Submit partner events to Service provider server.    -   iption    -   Meth        -   POST    -   od        -   x-login—username of the integration user.x-password—password            of the    -   Heade        -   integration user.x-partnerKey—A unique key issued by Service            provider to the    -   r        -   partner    -   URL        -   partnerName: The unique name of the            partner.externalAccountId: The user's    -   param        -   account ID in the partner system.    -   eters    -   Events originated from the partner system in IcEvent(s) JSON        format.Example:{“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”:        “acc_1234”},{“name”:“virtualDevice.instanceId”,“value”:“rachio-inst001        “},{”        name”:“virtualDevice.providerId”,“value”:“rachio”}],“mediaType”:“s        prinkler/on”,“ts”:1409675025053,“value”:“true”}]}    -   Fields:        -   mediaType: The event mediaTypes defined as part of the cloud            object    -   Body definition and approved by Service provider.        -   ts: The time when the event happened (in milliseconds).    -   Event metadata:        -   virtualDevice.providerId: The name of the partner. Also            referred to as Integration ID in the Card SDK.        -   virtualDevice.siteId: The user's account ID in the partner            system.        -   virtualDevice.instanceId: The device ID in the partner            system.            Result HTTP response 200 if successful.

In controlling a partner product via the rules engine (actions) of anembodiment, the CIS uses the partner's Event Callback URL to submitaction events to partner's system. Typically, an action event asks tothe partner's system to perform a specific function. The partner submitsthe result of the action back to Service provider in the form of anevent.

Payload Description

UR

-   -   The Event Callback URL for the partner        L        Des        crip Submit action events to partner server.        tion        Met    -   POST        hod    -   Authorization—The value is ‘Bearer xxxxxx’ with xxxxxx being the        user's OAUTH        Hea    -   access token.externalAccountId: The user's account ID in the        partner system (to be        der    -   added on Padre release).        UR    -   L        par    -   None.        am        eter    -   s    -   Action events originated from the Service provider system in        IcEvent JSON format.    -   Example event sent to Rachio:    -   {“icEvent”:[{“ts”:1409675025053,“instanceId”:“181964.0”,“mediaType”:“virtualDe        vice/pending”,“id”:“1430834677258”,“instanceName”:“Bedroom”,“value”:        null,“cont ext”:[        ],“metaData”:“name”:“virtualDevice.instanceId”,“value”:“rachio-inst001”},{“name”:“virtualDevice.siteId”,“value”:“acc_1234”},{“name”:“virtualDev        ice.providerId”,“value”:“rachio”},{“name”:“functionMediaType”,“value”:“sprinkler/schedulePause”},{“requestMessageId”},{“value”:“1430489036”}]}]}    -   Fields:        -   id: The event ID generated by Service provider server.        -   mediaType: All action events have ‘virtualDevice/pending’ as            the event media type. The actual action is represented as            ‘sprinkler/schedulePause’ in    -   Bo        -   metadata.    -   dy        -   ts: The time when the event happened (in milliseconds).        -   instanceId: The ID of the device in Service provider system.    -   Event metadata:        -   virtualDevice.providerId: The name of the partner. Also            referred to as Integration ID in the Card SDK.        -   virtualDevice.siteId: The user's account ID in the partner            system.        -   virtualDevice.instanceId: The device ID in the partner            system.        -   functionMediaType: Identifies the action called by Service            provider. The list of all possible function media types are            defined at the time of partner onboarding.        -   requestMessageId: The ID of the action request. Partner            should used the this ID when sending success/failure            response.    -   Upon receiving the action event, partner should send        success/failure response as event to Service provider server.    -   Successful response:        -   {“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”:“acc_1234”            },{“na    -   Act        -   me”:“virtualDevice.instanceId”,“value”:“rachio-    -   ion        -   inst001”},{“name”:“virtualDevice.providerId”,“value”:“rachio”},{“name”:“request    -   Eve        -   MessageId”,“value”:“1430489036”}],“mediaType”:“virtualDevice/success”,“ts”:140    -   nt        -   9675025053,“value”:“true”}]}    -   Res    -   pon        -   Failure Response:    -   se        -   {“icEvent”:[{“metaData”:[{“name”:“virtualDevice.siteId”,“value”:“acc_1234”},{“na            me”:“virtualDevice.instanceId”,“value”:“rachio-inst001”},{“name”:“virtualDevice.providerId”,“value”:“rachio”},{“name”:“request            MessageId”,“value”:“1430489036”}],“mediaType”:“virtualDevice/failed”,“ts”:14096            75025053,“errorCode”:“500”,“value”:“true”}]}

Event disposition is determined by the functionMediaType in the metaDataarray. In the above example, the functionMediaType has the value ofdevice/schedulePause, but depending on the function, there may be aparameter or value in order to effect the desired control.

FIG. 34 is a flow diagram for Service Disassociation, under anembodiment. If the user adds/removes a device in the Partner's system,the Partner Server calls the CIS API to inform Service provider aboutthe change. A Cloud Service can be disassociated from an Serviceprovider user through an API invocation on the Service provider server.This removes the cloud account and its associated Cloud devices from theService provider server. A SMAP message is sent to the CPE to update itsCloud Object inventory, and the CIS calls the partner's ‘Event CallbackURL’ to inform the Partner that the user has disassociated.

  Payload Description  URL   The Event Callback URL for the partner      Notify Partner Server that a user has “deleted” or removed one oftheir Description       partner products from being controlled by theService provider system.  Method  POST   URL       None Parameters      {        “icEvent”:[         {          “metaData”:[           {           “name”:“virtualDevice.siteId”,           “value”:“rachio-account-id-0001”,           },           {           “name”:“virtualDevice.instanceId”,           “value”:“rachio-userinst-0001”,           },           {Body         “name”:“virtualDevice.providerId”,           “value”:“rachio”,           },          ],         “id”:“1409865500000”,         “mediaType”:“virtualDevice/remove”,         “ts”:1409865500000,         “href”:“sites/1/network/instances/181002.0”,         “siteId”:“1”,          “deviceId”:“1002”,         “instanceId”:“181002.0”,         }        ]       }

Event metadata includes but is not limited to: virtualDevice.providerId(e.g., name of the partner, also referred to as Integration ID in theCard SDK); virtualDevice.siteId (e.g., user's account ID in the partnersystem); virtualDevice.instanceId (e.g., device ID in the partnersystem). Fields include but are not limited to: mediaType (e.g., allremove events will have a mediaType of ‘virtualDevice/remove’); is(e.g., time when the event happened (in milliseconds)); instanceId(e.g., ID of the device in Service provider system); id (e.g., event IDgenerated by Service provider server).

FIG. 35 is a flow diagram for Card UI Interactions, under an embodiment.The Card UIs that interact with the Cloud Objects will not depend ondata stored in Service provider servers. Instead the cards will interactthrough the Partner Proxy Service, which handles authentication andlogging, to make calls to the partner server. For example, a Nest cardthat needs to show a list of thermostats will get the list ofthermostats and their metadata indirectly from Nest (through the PartnerProxy Service) instead of leveraging the Cloud Object data stored in ourdatabase. This is done primarily due to the desire to have the Card UIauthors, which are expected to be the partners themselves, use their ownAPIs for easier development. Note that it does provide the possibilityfor the two data sets (the Cloud Objects in our database and the list ofdevices provided by the partner's server) to get out of sync if bugsexist in the integrations. Normally changes should be synchronized asdescribed above in Cloud Object Synchronization and the two data setsshould be equivalent.

Cards will be oblivious to authentication with the Partner Server(except for service association where the authentication data is storedin our server). Invocations to the Partner Proxy Service cause it toattempt a ‘pass-through’ invocation on the Partner Server using theauthentication credentials stored in the database. If the Partner Serverresponds with a 401 authentication failure, the Partner Proxy Servicewill attempt to refresh the token and re-attempt the invocation to thePartner Server with the updated token as shown in the diagram above.Authentication credentials are not made available to the Cards, so theyperform authenticated requests through the Partner Proxy Service.

The system of an embodiment includes files that form the CloudIntegration Metadata. As an example, an embodiment includes CloudIntegration Descriptor (CID) and Rules Template files that make up theCloud Integration Metadata that defines a cloud integration.

The CID describes the capabilities of the devices and/or servicesprovided by the Partner Provider Plugin including attributes, actions,events, and their associated parameters. This descriptor is used by theserver to provide REST API access to the capabilities provided by thecloud service, but is not so limited.

An example CID XSD of an embodiment is as follows, but the embodiment isnot so limited.

  CID XSD  <xs:complexType name=“cloudObject”>   <xs:complexContent>   <xs:sequence>     <xs:element name=“name” type=“xs:token”/>    <xs:element name=“metaData” type=“metaData” minOccurs=“0”maxOccurs=“64”/>     <xs:element name=“point” type=“point” minOccurs=“0”maxOccurs=“64”/>     <xs:element name=“function” type=“function”minOccurs=“0” maxOccurs=“64”/>    </xs:sequence>    <xs:attributename=“id” type=“xs:string” use=“required”/>    <xs:attributename=“mediaType” type=“xs:token” use=“optional”/>    <xs:attributename=“href” type=“xs:anyURI”/>    <xs:attribute name=“tags”type=“xs:token”/>    <xs:attribute name=“status”type=“cloudObjectStatus”/>   </xs:complexContent>  </xs:complexType> <xs:complexType name=“metaData”>   <xs:attribute name=“name”type=“xs:string”/>   <xs:attribute name=“value” type=“xs:string”/>  <xs:attribute name=“mediaType” type=“xs:token”/>  </xs:complexType> <xs:complexType name=“point”>   <xs:attribute name=“mediaType”type=“xs:token” use=“required”/>   <xs:attribute name=“name”type=“xs:string”/>   <xs:attribute name=“href” type=“xs:anyURI”/>  <xs:attribute name=“value” type=“xs:string”/>   <xs:attributename=“ts” type=“xsiong”/>   <xs:attribute name=“readOnly”type=“xs:boolean” use=“required”/>  </xs:complexType>  <xs:complexTypename=“function”>   <xs:sequence>    <xs:element name=“input”type=“input” minOccurs=“0” maxOccurs=“unbounded”/>   </xs:sequence>  <xs:attribute name=“mediaType” type=“xs:token” use=“required”/>  <xs:attribute name=“name” type=“xs:token”/>   <xs:attributename=“href” type=“xs:anyURI”/>   <xs:attribute name=“description”type=“xs:string”/>  </xs:complexType>  <xs:simpleTypename=“cloudObjectStatus”>   <xs:restriction base=“xs:token”>   <xs:enumeration value=“ok”/>    <xs:enumeration value=“offline”/>   <xs:enumeration value=“unknown”/>    <xs:enumerationvalue=“missing”/>    <xs:enumeration value=“searching”/>   <xs:enumeration value=“configuration_failure”/>    <xs:enumerationvalue=“upgrading”/>    <xs:enumeration value=“configuring”/>  </xs:restriction>  </xs:simpleType>

An example CID of an embodiment is as follows, but the embodiment is notso limited.

  Example CID <Nest id=“Nest343234345” mediaType=“cloud/nest”tags=“thermostat” status=“ok”>  <name>My Nest</name>  <metadataname=“manufacturer” mediaType=“cloud/nest/manufacturer” value=“Nest”/> <metadata name=“model” mediaType=“cloud/nest/model” value=“M1”/> <point name=“temperature” mediaType=“cloud/nest/temperature”value=“2800” ts=“23434535464557” readOnly=“false”/>  <pointname=“coolSetpoint” mediaType=“cloud/nest/coolSetpoint” value=“2400”ts=“23434535464557” readOnly=“false”/>  <point name=“heatSetpoint”mediaType=“cloud/nest/heatSetpoint” value=“2000” ts=“23434535464557”readOnly=“false”/>  <function name=“resetSetpoints”mediaType=“cloud/nest/reset” description=“reset heat/cool setpoint tofactory default”/> </Nest>

An example Rules XSD Changes of an embodiment is as follows, but theembodiment is not so limited.

  Rules XSD Changes  <!--   - Subclass of trigger for Cloud commands.  -->  <xsd:complexType name=“cloudTrigger”>   <xsd:complexContent>   <xsd:extension base=“trigger”>     <xsd:sequence>      <!-- - Thespecific cloud object ID. -->      <xsd:element name=“cloudObjectID”type=“xsd:string” minOccurs=“1” maxOccurs=“1”/>      <!-- the evaluationmechanism to apply to this trigger -->      <xsd:choice>      <xsd:element name=“simpleEval”type=“cloudSimpleTriggerEvaluation”/>       <xsd:elementname=“comparisonEval” type=“cloudComparisonTriggerEvaluation”/>     </xsd:choice>     </xsd:sequence>    </xsd:extension>  </xsd:complexContent>  </xsd:complexType>  <xsd:elementname=“cloudTrigger” type=“cloudTrigger” substitutionGroup=“trigger”/> <!-- simple cloud trigger evaluation (just an event, no args) --> <xsd:complexType name=“cloudSimpleTriggerEvaluation”>   <xsd:sequence>   <xsd:element name=“eventName” type=“xsd:string”/>   </xsd:sequence> </xsd:complexType>  <!-- cloud trigger evaluation that compares a value-->  <xsd:complexType name=“cloudComparisonTriggerEvaluation”>  <xsd:sequence>    <xsd:element name=“attributeName”type=“xsd:string”/>    <xsd:element name=“comparisonMethod”type=“comparisonMethodEnum”/>    <xsd:element name=“comparisonValue”type=“xsd:double”/>   </xsd:sequence>  </xsd:complexType>  <!--comparison methods -->  <xsd:simpleType name=“comparisonMethodEnum”>  <xsd:restriction base=“xsd:string”>    <!-- equality -->   <xsd:enumeration value=“eq”/>    <!-- less than -->   <xsd:enumeration value=“lt”/>    <!-- less than or equal -->   <xsd:enumeration value=“le”/>    <!-- greater than-->   <xsd:enumeration value=“gt”/>    <!-- greater than or equal -->   <xsd:enumeration value=“ge”/>   </xsd:restriction>  </xsd:simpleType>

An example Master Action List Changes of an embodiment is as follows,but the embodiment is not so limited.

  Master Action List Changes  <a:action actionID=“137”>  <a:description>Invoke a Cloud Action</a:description>  <a:parameterDef>    <a:key>cloudObjectID</a:key>   <a:type>string</a:type>   </a:parameterDef>   <a:parameterDef>   <a:key>cloudActionID</a:key>    <a:type>string</a:type>  </a:parameterDef>   <a:parameterDef>    <a:key>parameters</a:key>   <a:type>string</a:type> <!-- a JSONArray of    JSONObjects thatcontain name/value/type triplets (type is optional) -->  </a:parameterDef>   <!-- does this type make sense? -->  <a:type>workflow</a:type>  <a:target>ruleAction_invokeCloud</a:target>  </a:action>

An example Rule XML Examples of an embodiment is as follows, but theembodiment is not so limited.

  Rule XML Examples <rule ruleID=“1002351”>  <triggerList>  <cloudTrigger>    <description>Cloud Trigger</description>   <category>cloud</category>    <!-- just points to the global service,not to any particular instance -->   <cloudObjectID>AccuWeather</cloudObjectID>    <!-- it is assumed herethat when the AccuWeather account is connected     that it is alreadyfiltering based on the user's location / zipcode -->    <simpleEval>    <eventName>tornadoWarning</eventName>    </simpleEval>  </cloudTrigger>  </triggerList>  <action>   <actionID>70</actionID>  <parameter>    <key>lightID</key>    <value>3781220513309696</value>  </parameter>   <parameter>    <key>level</key>    <value>100</value>  </parameter>  </action>  <description>Turn on kitchen light whenTornado Warning</description> </rule> <rule ruleID=“1008603”> <triggerList>   <zoneTrigger>    <description>ZoneTrigger</description>    <category>sensor</category>   <zoneState>open</zoneState>    <zoneID>18</zoneID>   </zoneTrigger> </triggerList>  <action>   <actionID>137</actionID>   <parameter>   <key>cloudObjectID</key>    <value>nest.1</value> <!-- device 1 underthe nest service associated with this account -->   </parameter>  <parameter>    <key>cloudActionID</key>   <value>configureThermostat</value>   </parameter>   <parameter>   <key>parameters</key>    <value>[ { “name”: “heatSetPoint”, “value”:“2200”, “type”: “nest/temperature” }, { “name”: “coolSetPoint”, “value”:“2700” } ] </value>   </parameter>  </action>  <description>Zone 1 OpenConfigure Nest Thermostat</description> </rule>

In order to provide a dynamic list of available actions and triggersduring rule authoring, templates describing the available functionalitymust be provided with the Cloud Integration Metadata. Some examples oftrigger and action templates (e.g., Rachio Smart Sprinkler Controllertrigger and action template, AccuWeather weather service triggertemplate, etc.) of an embodiment are as follows, but the embodiment isnot so limited.

  Example Rule Templates <rules-core:triggerTemplates    xmlns:rules-core=“rules-core”xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”    xsi:schemaLocation=“rules-core../../../../rules-core/src/main/resources/rules- core.xsd”>    <rules-core:triggerTemplate id=“203”    description=“{STR.RULES.TEMPLATES.TRIGGER.DESC.INSTANCE.RAC HIO}”        cvTriggerType=“cloudTrigger” cvCategory=“cloud”    excludeActionIds=“10:11:15:16:17:18:100:101:103:120:121:122:135:136:137:138:139”>         <rules-core:inputs>             <rules-core:inputhidden=“false”    description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.DESC.RACHIO}”                 name=“targetValues” pattern=“eq”>                <option    description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPTION.DESC.RACHIO.ON}”                     value=“1” />                <option    description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPTION.DESC.RACHIO.OFF}”                     value=“0” />            </rules-core:input>             <rules-core:inputhidden=“true” name=“type” value=“event” />             <rules-core:inputhidden=“false” name=“instanceIds” />             <rules-core:inputhidden=“true” name=“tags” value=“rachio” />            <rules-core:input hidden=“true” name=“mediaTypes”                value=“sprinkler/on” />         </rules-core:inputs>    </rules-core:triggerTemplate> </rules-core:triggerTemplates><rules-core:triggerTemplates     xmlns:rules-core=“rules-core”xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”    xsi:schemaLocation=“rules-core../../../../rules-core/src/main/resources/rules- core.xsd”>    <rules-core:triggerTemplate id=“200”    description=“{STR.RULES.TEMPLATES.TRIGGER.DESC.INSTANCE.ACCUWEATHER}”         cvTriggerType=“cloudTrigger” cvCategory=“cloud”excludeActionIds=“10:11:15:16:17:18:135:136”>        <rules-core:inputs>             <rules-core:input hidden=“false”    description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.DESC.ACCUWEATHER}”                 name=“targetValues” pattern=“gt”>                <option    description=“{STR.RULES.TEMPLATES.TRIGGER.TARGETVALUES.OPTION.DESC.ACCUWEATHER.TEMPERATURE.GT}”                    value=“temperatureGt” />            </rules-core:input>             <rules-core:inputhidden=“true” name=“type“value=“event” />             <rules-core:inputhidden=“false” name=“instanceIds” />             <rules-core:inputhidden=“true” name=“tags” value=“accuWeather” />            <rules-core:input hidden=“true” name=“mediaTypes”                value=“weather/temperature” />        </rules-core:inputs>     </rules-core:triggerTemplate></rules-core:triggerTemplates> <rules-core:actionTemplatesxmlns:rules-core=“rules-core”    xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”    xsi:schemaLocation=“rules-core../../../../rules-core/src/main/resources/rules- core.xsd”>    <rules-core:actionTemplate id=“137”    description=“{STR.RULES.TEMPLATES.ACTION.DESC.RACHIO.OFF}”cvActionId=“137”         cvType=“workflow”>         <rules-core:inputs>            <rules-core:input hidden=“false” description=“Which RachioObject”                 name=“instanceIds” cvKey=“cloudObjectID”cvType=“cloudObjectID”                 cvRequired=“true“/>            <rules-core:input name=“mediaType”value=“sprinkler/scheduleStop” />         </rules-core:inputs>    </rules-core:actionTemplate> </rules-core:actionTemplates>Sample curl commands of Rachio cloud rule follows.curl -k -v -L -H “Content-Type:application/json”-H “X-login:insight”-H“X-password:test”-H “X-AppKey: defaultKey”-X PUT“https://10.0.12.102/rest/icontrol/sites/420/rules”-d‘{“description”:“Rachio turns ON,Turn onLight”,“executionSource”:“client”,“enabled”:true,“valid”:true,“default”:false,“conditionals”:{“conditional”:[{“triggers”:{“trigger”:[{“description”:“Rachio isON”,“id”:“0”,“templateId”:“203”,“targetValues”:“1”,“type”:“event”,“mediaTypes”:“sprinkler/systemOn”,“instances”:“181002.0”,“targetComparisonTypes”:“eq”}]},“actions”:{“action”:[{“id”:“0”,“templateId”:“70”,“inputs”:“level=0&”,“instanceIds”:“13000d6f00020a5d9a.1.0”}]}}]}}’User should pass targetComparisonTypes whenever there is a patternpresent in cloudTrigger. In above case targetComparisonTypes is “eq” andtargetValues is “1”.Both these values should be fetched from the triggerTemplate.Sample curl commands of AccuWeather cloud rule follows.curl-k -v -L -H “Content-Type:application/json”-H “X-login:insight”-H“X-password:test”-H “X-AppKey: defaultKey”-X PUT“https://10.0.12.102/rest/icontrol/sites/420/rules”-d‘{“description”:“Outside temperature is less than 100, Turn onlight”,“executionSource”:“client”,“enabled”:true,“valid”:true,“default”:false,“conditionals”:{“conditional”:[{“triggers”:{“trigger”:[{“description”:“Outsidetemperature is greater than 60 degrees, turn onlight”,“id”:“0”,“templateId”:“200”,“targetValues”:“70”,“type”:“event”,“mediaTypes”:“weather/temperature”,“instances”:“181001.0”,“targetComparisonTypes”:“gt”}]},“actions”:{“action”:[{“id”:“0”,“templateId”:“70”,“inputs”:“level=0&”,“instanceIds”:“13000d6f00020a5d9a.1.0”}]}}]}}’In above case targetComparisonTypes is “gt” and targetValues is “70”.Here targetComparisonTypes should be fetched from triggerTemplate anduser should pass user defined value in targetValues.SMAP Protocol Changes

SMAP is updated to allow server to send external events to CPE and CPEsend external action event to server.

  <xsd:complexType name=“cloudEvent”>   <xsd:complexContent>   <xsd:extension base=“smap:baseMessage”>     <xsd:sequence>     <xsd:element name=“metaData” type=“smap:eventMetaData”maxOccurs=“32” minOccurs=“0”>       <xsd:annotation>       <xsd:documentation>Additional information about the eventitself</xsd:documentation>       </xsd:annotation>      </xsd:element>     <xsd:element name=“context” type=“smap:eventContext” maxOccurs=“32”minOccurs=“0”>       <xsd:annotation>       <xsd:documentation>Information about other aspects of the systemat the time of the event</xsd:documentation>        </xsd:annotation>     </xsd:element>     </xsd:sequence>     <xsd:attribute name=“id”type=“xsd:token”/>     <xsd:attribute name=“cloudObjectId”type=“xsd:token”/>     <xsd:attribute name=“mediaType” type=“xsd:token”use=“required”/>     <xsd:attribute name=“ts” type=“xsd:long”use=“required”/>     <xsd:attribute name=“href” type=“xsd:anyURI”/>    <xsd:attribute name=“errorCode” type=“xsd:token”/>    <xsd:attribute name=“value” type=“xsd:string”/>    </xsd:extension>  </xsd:complexContent>  </xsd:complexType>  <xsd:complexTypename=“eventContext”>   <xsd:attribute name=“mediaType” type=“xsd:token”use=“required”/>   <xsd:attribute name=“value” type=“xsd:string”use=“required”/>   <xsd:attribute name=“href” type=“xsd:anyURI”/> </xsd:complexType>  <xsd:complexType name=“eventMetaData”>  <xsd:attribute name=” name” type=“xsd:token” use=“required”/>  <xsd:attribute name=“value” type=“xsd:string” use=“required”/> </xsd:complexType>  <xsd:complexType name=“cloudActionEvent”>  <xsd:complexContent>    <xsd:extension base=“smap:baseMessage”>    <xsd:sequence>      <xsd:element name=“ruleId” type=“xsd:long”minOccurs=“0” maxOccurs=“1”>       <xsd:annotation>       <xsd:documentation>Id of the rule that triggered this action, ifapplicable.</xsd:documentation>       </xsd:annotation>     </xsd:element>      <xsd:element name=“eventId” type=“xsd:string”minOccurs=“0” maxOccurs=“1”>       <xsd:annotation>       <xsd:documentation>The id of the event that triggered therule.</xsd:documentation>       </xsd:annotation>      </xsd:element>     <xsd:element name=“cloudObjectId” type=“xsd:token” minOccurs=“1”maxOccurs=“1”/>      <xsd:element name=“actionMediaType”type=“xsd:token” minOccurs=“1” maxOccurs=“1”/>      <xsd:elementname=“actionHrer type=“xsd:anyURI” minOccurs=“0” maxOccurs=“1”/>     <xsd:element name=“actionInput” type=“smapinput” minOccurs=“0”maxOccurs=“32”/>     </xsd:sequence>    </xsd:extension>  </xsd:complexContent>  </xsd:complexType>  <xsd:complexTypename=“input”>   <xsd:attribute name=“name” type=“xsd:token”use=“required”/>   <xsd:attribute name=“mediaType” type=“xsd:token”use=“optional”/>   <xsd:attribute name=“value” type=“xsd:string”use=“required”/>  </xsd:complexType>

The ICS of an embodiment effects ICS platform integration with thirdparty system and device functionality (e.g., Philips Hue lights,Chamberlain garage door openers, Nest thermostats, Dropcam cameras,Doorbot doorbell cameras, etc.), as described in detail herein. Usingthe same processes, other server-to-server (cloud) services (e.g.,Accuweather, MSO digital assets such as voicemail, etc.) are alsointegrated into the ICS platform.

Cloud Actions and Triggers of an embodiment enable cloud services andinternet-connected devices to leverage the user interface, Rules Engineand other functions of the service provider system. This allows thirdparty devices (e.g., smart door bells, door locks, garage dooroperators, cameras, thermostats, lighting systems, lighting devices,lawn irrigation systems, plant sensors, pet feeders, weather stations,rain sensors, pool controls, air quality sensors, music systems, remotecontrollers, internet user interfaces, connected systems, connectedvehicles, etc.), third party services (e.g., weather forecastingservices and applications, family networking services and applications,etc.), and others to trigger automations in the service provider systemusing the Rules Engine. This enables end-users to integrate and usetheir previously-standalone internet connected devices with theirservice provider-based service.

FIG. 36 is an example rules interface for controlling triggers andactions involving third party devices integrated in the CAT, under anembodiment. FIG. 37 is an example of a triggers portion of a rulesinterface for third party services integrated with the CAT, under anembodiment. FIG. 38 is another example of an actions portion of a rulesinterface for integrated third party devices, under an embodiment. Therules automation actions and triggers of an embodiment includemonitor/control functionality enabled via proprietary UIs, and withcards in the Card UI as described herein.

Embodiments include a system comprising a cloud hub located in apremises. The cloud hub comprises a plurality of adapters coupled to aplurality of premises devices. The cloud hub is configured as a gatewayfor the premises devices. The system includes a virtual gateway locatedin a cloud server environment and coupled to the cloud hub. The virtualgateway is configured as a server-side abstraction of the cloud hub. Thecloud hub and the virtual gateway are configured as an automationplatform that maintains state data of the plurality of premises devices,controls interaction among the plurality of premises devices, andmonitors and manages the plurality of premises devices.

Embodiments include a system comprising: a cloud hub located in apremises, wherein the cloud hub comprises a plurality of adapterscoupled to a plurality of premises devices, wherein the cloud hub isconfigured as a gateway for the premises devices; a virtual gatewaylocated in a cloud server environment and coupled to the cloud hub,wherein the virtual gateway is configured as a server-side abstractionof the cloud hub, wherein the cloud hub and the virtual gateway areconfigured as an automation platform that maintains state data of theplurality of premises devices, controls interaction among the pluralityof premises devices, and monitors and manages the plurality of premisesdevices.

The plurality of adapters includes an internet protocol (IP) adapter.

The IP adapter is coupled to a premises device including at least one IPdevice.

The plurality of adapters includes a radio adapter.

The radio adapter is configured to use a communication protocol of apremises device coupled to the radio adapter.

The radio adapter includes a wireless radio adapter.

The radio adapter is coupled to a premises device including at least oneZigbee device.

The plurality of adapters includes a camera adapter.

The camera adapter is coupled to a premises device including at leastone camera device.

The at least one camera device includes a tunnel camera.

The plurality of adapters include a Wi-Fi adapter.

The cloud hub is coupled to a radio frequency (RF) bridge in thepremises.

The RF bridge is coupled to at least one additional premises device.

The at least one additional premises device includes at least one Z-Wavedevice.

The cloud server environment includes a session server, wherein thevirtual gateway is an instance of a plurality of virtual gatewaysrunning on the session server.

The cloud server environment includes at least one of a registry gatewayand a session gateway, wherein the at least one the registry gateway anda session gateway are coupled to the session server.

The registry gateway is configured to identify the virtual gateway fromthe plurality of virtual gateways and route incoming data from the cloudhub to the virtual gateway.

The routing of incoming data includes a mapping of premises deviceidentification (ID) and device type to site ID corresponding to thepremises.

The premises device ID corresponds to at least one of the plurality ofpremises devices.

The site ID is assigned to the cloud hub.

The cloud hub is configured to communicate with the registry gateway andreceive the site ID.

The cloud hub is configured to communicate with the registry gateway andreceive a network address of the credential gateway.

The cloud server environment includes a credential gateway, wherein thecloud hub is configured to communicate with the credential gateway and,using the site ID, receive a key.

The cloud hub is configured to receive session server data from thecredential gateway, wherein the session server data includes a sessionserver address.

The virtual gateway comprises a first gateway state machine running onthe session server.

The cloud hub comprises a processor running a second gateway statemachine.

At least one of the first gateway state machine and the second gatewaystate machine maintains track of a state of the plurality of premisesdevices.

At least one of the first gateway state machine and the second gatewaystate machine monitors and manages the plurality of premises devices.

The first gateway state machine and the second gateway state machinemaintain track of a state of the plurality of premises devices.

The first gateway state machine and the second gateway state machinemonitor and manage the plurality of premises devices.

The system includes at least one premises device of the plurality ofpremises devices configured to communicate with the virtual gateway overa cellular coupling.

Inbound communications to the virtual gateway comprise packetcommunications.

Outbound communications from the virtual gateway comprise short messageservice (SMS) messages.

The cloud hub is configured to maintain a persistent connection with thecloud server environment.

The cloud hub is coupled to the cloud server environment using abroadband coupling.

The cloud hub is coupled to the cloud server environment using acellular coupling.

The system includes a remote device coupled to the cloud serverenvironment, wherein the remote device receives state data of theplurality of premises devices and provides control data to the pluralityof premises devices.

The remote device is coupled to the cloud server via at least one of amobile portal and a web portal.

The plurality of premises devices includes at least one of a sensor, adetector, a camera, an input/output (I/O) device, a touchscreencontroller, a video camera, an input/output (I/O) device, an actuator,and a device controller that controls an attached device.

Embodiments include a method comprising configuring a cloud hub toinclude a plurality of adapters. The plurality of adapters is coupled toa plurality of premises devices. The cloud hub is located in a premisesand configured as a gateway for the premises devices. The methodincludes configuring a cloud server environment to include a virtualgateway. The virtual gateway is coupled to the cloud hub and configuredas a server-side abstraction of the cloud hub. The method includesconfiguring the cloud hub and the virtual gateway as an automationplatform that maintains state data of the plurality of premises devices,controls interaction among the plurality of premises devices, andmonitors and manages the plurality of premises devices.

Embodiments include a method comprising: configuring a cloud hub toinclude a plurality of adapters, wherein the plurality of adapters iscoupled to a plurality of premises devices, wherein the cloud hub islocated in a premises and configured as a gateway for the premisesdevices; configuring a cloud server environment to include a virtualgateway, wherein the virtual gateway is coupled to the cloud hub andconfigured as a server-side abstraction of the cloud hub; configuringthe cloud hub and the virtual gateway as an automation platform thatmaintains state data of the plurality of premises devices, controlsinteraction among the plurality of premises devices, and monitors andmanages the plurality of premises devices.

The plurality of adapters includes an internet protocol (IP) adapter.

The IP adapter is coupled to a premises device including at least one IPdevice.

The plurality of adapters includes a radio adapter.

The method includes configuring the radio adapter to use a communicationprotocol of a premises device coupled to the radio adapter.

The radio adapter includes a wireless radio adapter.

The radio adapter is coupled to a premises device including at least oneZigbee device.

The plurality of adapters includes a camera adapter.

The camera adapter is coupled to a premises device including at leastone camera device.

The at least one camera device includes a tunnel camera.

The plurality of adapters include a Wi-Fi adapter.

The cloud hub is coupled to a radio frequency (RF) bridge in thepremises.

The RF bridge is coupled to at least one additional premises device.

The at least one additional premises device includes at least one Z-Wavedevice.

The method includes configuring the cloud server environment to includea session server, wherein the virtual gateway is an instance of aplurality of virtual gateways running on the session server.

The method includes configuring the cloud server environment to includeat least one of a registry gateway and a session gateway, wherein the atleast one of the registry gateway and the session gateway are coupled tothe session server.

The method includes configuring the registry gateway to identify thevirtual gateway from the plurality of virtual gateways and routeincoming data from the cloud hub to the virtual gateway.

The method includes configuring the routing of incoming data to includea mapping of premises device identification (ID) and device type to siteID corresponding to the premises.

The premises device ID corresponds to at least one of the plurality ofpremises devices.

The site ID is assigned to the cloud hub.

The method includes configuring the cloud hub to communicate with theregistry gateway and receive the site ID.

The method includes configuring the cloud hub to communicate with theregistry gateway and receive a network address of the credentialgateway.

The method includes configuring the cloud server environment to includea credential gateway, and configuring the cloud hub to communicate withthe credential gateway and, using the site ID, receive a key.

The method includes configuring the cloud hub to receive session serverdata from the credential gateway, wherein the session server dataincludes a session server address.

The method includes configuring the virtual gateway to include a firstgateway state machine running on the session server.

The method includes configuring the cloud hub to include a processorrunning a second gateway state machine.

The method includes configuring at least one of the first gateway statemachine and the second gateway state machine to maintain track of astate of the plurality of premises devices.

The method includes configuring at least one of the first gateway statemachine and the second gateway state machine to monitor and manage theplurality of premises devices.

The method includes configuring the first gateway state machine and thesecond gateway state machine to maintain track of a state of theplurality of premises devices.

The method includes configuring the first gateway state machine and thesecond gateway state machine to monitor and manage the plurality ofpremises devices.

The method includes configuring at least one premises device of theplurality of premises devices to communicate with the virtual gatewayover a cellular coupling.

The method includes configuring inbound communications to the virtualgateway to include packet communications.

The method includes configuring outbound communications from the virtualgateway to include short message service (SMS) messages.

The method includes configuring the cloud hub to maintain a persistentconnection with the cloud server environment.

The cloud hub is coupled to the cloud server environment using abroadband coupling.

The cloud hub is coupled to the cloud server environment using acellular coupling.

The method includes a remote device coupled to the cloud serverenvironment, wherein the remote device receives state data of theplurality of premises devices and provides control data to the pluralityof premises devices.

The remote device is coupled to the cloud server via at least one of amobile portal and a web portal.

The plurality of premises devices includes at least one of a sensor, adetector, a camera, an input/output (I/O) device, a touchscreencontroller, a video camera, an input/output (I/O) device, an actuator,and a device controller that controls an attached device.

Embodiments include a system comprising a cloud hub located in apremises. The cloud hub comprises a plurality of adapters coupled to aplurality of premises devices. The cloud hub is configured as a gatewayfor the premises devices. The system includes a virtual gateway locatedin a cloud server environment and coupled to the cloud hub. The virtualgateway is configured as a server-side abstraction of the cloud hub. Thecloud hub and the virtual gateway are configured as an automationplatform that maintains state data of the plurality of premises devices,controls interaction among the plurality of premises devices, andmonitors and manages the plurality of premises devices. The systemincludes a security system coupled to the virtual gateway. The securitysystem includes a plurality of security system components.

Embodiments include a system comprising: a cloud hub located in apremises, wherein the cloud hub comprises a plurality of adapterscoupled to a plurality of premises devices, wherein the cloud hub isconfigured as a gateway for the premises devices; a virtual gatewaylocated in a cloud server environment and coupled to the cloud hub,wherein the virtual gateway is configured as a server-side abstractionof the cloud hub, wherein the cloud hub and the virtual gateway areconfigured as an automation platform that maintains state data of theplurality of premises devices, controls interaction among the pluralityof premises devices, and monitors and manages the plurality of premisesdevices; a security system coupled to the virtual gateway, wherein thesecurity system includes a plurality of security system components.

The plurality of adapters includes an internet protocol (IP) adapter.

The IP adapter is coupled to a premises device including at least one IPdevice.

The plurality of adapters includes a radio adapter.

The radio adapter is configured to use a communication protocol of apremises device coupled to the radio adapter.

The radio adapter includes a wireless radio adapter.

The radio adapter is coupled to a premises device including at least oneZigbee device.

The plurality of adapters includes a camera adapter.

The camera adapter is coupled to a premises device including at leastone camera device.

The at least one camera device includes a tunnel camera.

The plurality of adapters include a Wi-Fi adapter.

The cloud hub is coupled to a radio frequency (RF) bridge in thepremises.

The RF bridge is coupled to at least one additional premises device.

The at least one additional premises device includes at least one Z-Wavedevice.

The cloud server environment includes a session server, wherein thevirtual gateway is an instance of a plurality of virtual gatewaysrunning on the session server.

The cloud server environment includes at least one of a registry gatewayand a session gateway, wherein the at least one the registry gateway anda session gateway are coupled to the session server.

The registry gateway is configured to identify the virtual gateway fromthe plurality of virtual gateways and route incoming data from the cloudhub to the virtual gateway.

The routing of incoming data includes a mapping of premises deviceidentification (ID) and device type to site ID corresponding to thepremises.

The premises device ID corresponds to at least one of the plurality ofpremises devices.

The site ID is assigned to the cloud hub.

The cloud hub is configured to communicate with the registry gateway andreceive the site ID.

The cloud hub is configured to communicate with the registry gateway andreceive a network address of the credential gateway.

The cloud server environment includes a credential gateway, wherein thecloud hub is configured to communicate with the credential gateway and,using the site ID, receive a key.

The cloud hub is configured to receive session server data from thecredential gateway, wherein the session server data includes a sessionserver address.

The virtual gateway comprises a first gateway state machine running onthe session server.

The cloud hub comprises a processor running a second gateway statemachine.

At least one of the first gateway state machine and the second gatewaystate machine maintains track of a state of the plurality of premisesdevices.

A least one of the first gateway state machine and the second gatewaystate machine monitors and manages the plurality of premises devices.

The first gateway state machine and the second gateway state machinemaintain track of a state of the plurality of premises devices.

The first gateway state machine and the second gateway state machinemonitor and manage the plurality of premises devices.

The system includes at least one premises device of the plurality ofpremises devices configured to communicate with the virtual gateway overa cellular coupling.

Inbound communications to the virtual gateway comprise packetcommunications.

Outbound communications from the virtual gateway comprise short messageservice (SMS) messages.

The cloud hub is configured to maintain a persistent connection with thecloud server environment.

The cloud hub is coupled to the cloud server environment using abroadband coupling.

The cloud hub is coupled to the cloud server environment using acellular coupling.

The system includes a remote device coupled to the cloud serverenvironment, wherein the remote device receives state data of theplurality of premises devices and provides control data to the pluralityof premises devices.

The remote device is coupled to the cloud server via at least one of amobile portal and a web portal.

The plurality of premises devices includes at least one of a sensor, adetector, a camera, an input/output (I/O) device, a touchscreencontroller, a video camera, an input/output (I/O) device, an actuator,and a device controller that controls an attached device.

At least one of the cloud hub and the virtual gateway is configured tomaintain state data of the security system, and control interactionamong the plurality of premises devices and the security system.

The security system is coupled to the virtual gateway using at least oneof a broadband coupling and a cellular coupling.

The security system is coupled to the virtual gateway using a broadbandcoupling.

The cloud hub is coupled to the gateway using a cellular coupling.

The cloud server environment includes a security server.

The plurality of security system components includes at least one of asensor, a detector, a camera, an input/output (I/O) device, and atouchscreen.

The plurality of security system components includes at least one of anInternet Protocol (IP) device, a video camera, an input/output (I/O)device, an actuator, and a device controller that controls an attacheddevice.

Embodiments include a method comprising configuring a cloud hub toinclude a plurality of adapters. The plurality of adapters is coupled toa plurality of premises devices. The cloud hub is located in a premisesand configured as a gateway for the premises devices. The methodincludes configuring a cloud server environment to include a virtualgateway. The virtual gateway is coupled to the cloud hub and configuredas a server-side abstraction of the cloud hub. The method includesconfiguring the cloud hub and the virtual gateway as an automationplatform that maintains state data of the plurality of premises devices,controls interaction among the plurality of premises devices, andmonitors and manages the plurality of premises devices. The methodincludes configuring a coupling between the virtual gateway and asecurity system in the premises, wherein the security system includes aplurality of security system components.

Embodiments include a method comprising: configuring a cloud hub toinclude a plurality of adapters, wherein the plurality of adapters iscoupled to a plurality of premises devices, wherein the cloud hub islocated in a premises and configured as a gateway for the premisesdevices; configuring a cloud server environment to include a virtualgateway, wherein the virtual gateway is coupled to the cloud hub andconfigured as a server-side abstraction of the cloud hub; configuringthe cloud hub and the virtual gateway as an automation platform thatmaintains state data of the plurality of premises devices, controlsinteraction among the plurality of premises devices, and monitors andmanages the plurality of premises devices; configuring a couplingbetween the virtual gateway and a security system in the premises,wherein the security system includes a plurality of security systemcomponents.

The plurality of adapters includes an internet protocol (IP) adapter.

The IP adapter is coupled to a premises device including at least one IPdevice.

The plurality of adapters includes a radio adapter.

The method includes configuring the radio adapter to use a communicationprotocol of a premises device coupled to the radio adapter.

The radio adapter includes a wireless radio adapter.

The radio adapter is coupled to a premises device including at least oneZigbee device.

The plurality of adapters includes a camera adapter.

The camera adapter is coupled to a premises device including at leastone camera device.

The at least one camera device includes a tunnel camera.

The plurality of adapters include a Wi-Fi adapter.

The cloud hub is coupled to a radio frequency (RF) bridge in thepremises.

The RF bridge is coupled to at least one additional premises device.

The at least one additional premises device includes at least one Z-Wavedevice.

The method includes configuring the cloud server environment to includea session server, wherein the virtual gateway is an instance of aplurality of virtual gateways running on the session server.

The method includes configuring the cloud server environment to includeat least one of a registry gateway and a session gateway, wherein the atleast one the registry gateway and a session gateway are coupled to thesession server.

The method includes configuring the registry gateway to identify thevirtual gateway from the plurality of virtual gateways and routeincoming data from the cloud hub to the virtual gateway.

The method includes configuring the routing of incoming data to includea mapping of premises device identification (ID) and device type to siteID corresponding to the premises.

The premises device ID corresponds to at least one of the plurality ofpremises devices.

The site ID is assigned to the cloud hub.

The method includes configuring the cloud hub to communicate with theregistry gateway and receive the site ID.

The method includes configuring the cloud hub to communicate with theregistry gateway and receive a network address of the credentialgateway.

The method includes configuring the cloud server environment to includea credential gateway, and configuring the cloud hub to communicate withthe credential gateway and, using the site ID, receive a key.

The method includes configuring the cloud hub to receive session serverdata from the credential gateway, wherein the session server dataincludes a session server address.

The method includes configuring the virtual gateway to comprise a firstgateway state machine running on the session server.

The method includes configuring the cloud hub to include a processorrunning a second gateway state machine.

The method includes configuring at least one of the first gateway statemachine and the second gateway state machine to maintain track of astate of the plurality of premises devices.

The method includes configuring at least one of the first gateway statemachine and the second gateway state machine to monitor and manage theplurality of premises devices.

The method includes configuring the first gateway state machine and thesecond gateway state machine to maintain track of a state of theplurality of premises devices.

The method includes configuring the first gateway state machine and thesecond gateway state machine to monitor and manage the plurality ofpremises devices.

The method includes configuring at least one premises device of theplurality of premises devices to communicate with the virtual gatewayover a cellular coupling.

The method includes configuring inbound communications to the virtualgateway to include packet communications.

The method includes configuring outbound communications from the virtualgateway to include short message service (SMS) messages.

The method includes configuring the cloud hub to maintain a persistentconnection with the cloud server environment.

The method includes configuring the cloud hub to couple to the cloudserver environment using a broadband coupling.

The method includes configuring the cloud hub to couple to the cloudserver environment using a cellular coupling.

The method includes configuring the cloud server environment to coupleto a remote device, wherein the remote device receives state data of theplurality of premises devices and provides control data to the pluralityof premises devices.

The remote device is coupled to the cloud server via at least one of amobile portal and a web portal.

The plurality of premises devices includes at least one of a sensor, adetector, a camera, an input/output (I/O) device, a touchscreencontroller, a video camera, an input/output (I/O) device, an actuator,and a device controller that controls an attached device.

The method includes configuring at least one of the cloud hub and thevirtual gateway to maintain state data of the security system, andcontrol interaction among the plurality of premises devices and thesecurity system.

The security system is coupled to the virtual gateway using at least oneof a broadband coupling and a cellular coupling.

The security system is coupled to the virtual gateway using a broadbandcoupling.

The method includes configuring the cloud hub to couple to the gatewayusing a cellular coupling.

The method includes configuring the cloud server environment to includea security server.

The plurality of security system components includes at least one of asensor, a detector, a camera, an input/output (I/O) device, and atouchscreen.

The plurality of security system components includes at least one of anInternet Protocol (IP) device, a video camera, an input/output (I/O)device, an actuator, and a device controller that controls an attacheddevice.

As described above, computer networks suitable for use with theembodiments described herein include local area networks (LAN), widearea networks (WAN), Internet, or other connection services and networkvariations such as the world wide web, the public internet, a privateinternet, a private computer network, a public network, a mobilenetwork, a cellular network, a value-added network, and the like.Computing devices coupled or connected to the network may be anymicroprocessor controlled device that permits access to the network,including terminal devices, such as personal computers, workstations,servers, mini computers, main-frame computers, laptop computers, mobilecomputers, palm top computers, hand held computers, mobile phones, TVset-top boxes, or combinations thereof. The computer network may includeone of more LANs, WANs, Internets, and computers. The computers mayserve as servers, clients, or a combination thereof.

The system can be a component of a single system, multiple systems,and/or geographically separate systems. The system can also be asubcomponent or subsystem of a single system, multiple systems, and/orgeographically separate systems. The system can be coupled to one ormore other components (not shown) of a host system or a system coupledto the host system.

One or more components of the system and/or a corresponding system orapplication to which the system is coupled or connected includes and/orruns under and/or in association with a processing system. Theprocessing system includes any collection of processor-based devices orcomputing devices operating together, or components of processingsystems or devices, as is known in the art. For example, the processingsystem can include one or more of a portable computer, portablecommunication device operating in a communication network, and/or anetwork server. The portable computer can be any of a number and/orcombination of devices selected from among personal computers, personaldigital assistants, portable computing devices, and portablecommunication devices, but is not so limited. The processing system caninclude components within a larger computer system.

The processing system of an embodiment includes at least one processorand at least one memory device or subsystem. The processing system canalso include or be coupled to at least one database. The term“processor” as generally used herein refers to any logic processingunit, such as one or more central processing units (CPUs), digitalsignal processors (DSPs), application-specific integrated circuits(ASIC), etc. The processor and memory can be monolithically integratedonto a single chip, distributed among a number of chips or components,and/or provided by some combination of algorithms. The methods describedherein can be implemented in one or more of software algorithm(s),programs, firmware, hardware, components, circuitry, in any combination.

The components of any system that includes the system herein can belocated together or in separate locations. Communication paths couplethe components and include any medium for communicating or transferringfiles among the components. The communication paths include wirelessconnections, wired connections, and hybrid wireless/wired connections.The communication paths also include couplings or connections tonetworks including local area networks (LANs), metropolitan areanetworks (MANs), wide area networks (WANs), proprietary networks,interoffice or backend networks, and the Internet. Furthermore, thecommunication paths include removable fixed mediums like floppy disks,hard disk drives, and CD-ROM disks, as well as flash RAM, UniversalSerial Bus (USB) connections, RS-232 connections, telephone lines,buses, and electronic mail messages.

Aspects of the systems and methods described herein may be implementedas functionality programmed into any of a variety of circuitry,including programmable logic devices (PLDs), such as field programmablegate arrays (FPGAs), programmable array logic (PAL) devices,electrically programmable logic and memory devices and standardcell-based devices, as well as application specific integrated circuits(ASICs). Some other possibilities for implementing aspects of thesystems and methods include: microcontrollers with memory (such aselectronically erasable programmable read only memory (EEPROM)),embedded microprocessors, firmware, software, etc. Furthermore, aspectsof the systems and methods may be embodied in microprocessors havingsoftware-based circuit emulation, discrete logic (sequential andcombinatorial), custom devices, fuzzy (neural) logic, quantum devices,and hybrids of any of the above device types. Of course the underlyingdevice technologies may be provided in a variety of component types,e.g., metal-oxide semiconductor field-effect transistor (MOSFET)technologies like complementary metal-oxide semiconductor (CMOS),bipolar technologies like emitter-coupled logic (ECL), polymertechnologies (e.g., silicon-conjugated polymer and metal-conjugatedpolymer-metal structures), mixed analog and digital, etc.

It should be noted that any system, method, and/or other componentsdisclosed herein may be described using computer aided design tools andexpressed (or represented), as data and/or instructions embodied invarious computer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of the above describedcomponents may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of embodiments of the systems and methods is notintended to be exhaustive or to limit the systems and methods to theprecise forms disclosed. While specific embodiments of, and examplesfor, the systems and methods are described herein for illustrativepurposes, various equivalent modifications are possible within the scopeof the systems and methods, as those skilled in the relevant art willrecognize. The teachings of the systems and methods provided herein canbe applied to other systems and methods, not only for the systems andmethods described above.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. These and other changes can bemade to the systems and methods in light of the above detaileddescription.

The invention claimed is:
 1. A method comprising: receiving, by a firstsession server of a plurality of session servers located external to apremises, wherein each session server of the plurality of sessionservers is configured to host one or more virtual gateways, and from apremises management system located at the premises, a message indicatingstate data associated with the premises management system; determining,by the first session server and based on the message, a second sessionserver of the plurality of session servers hosting a first virtualgateway associated with the premises management system and a thirdsession server of the plurality of session servers hosting a secondvirtual gateway associated with the first premises management system;causing, by the first session server, shutdown of the second virtualgateway on the third session server; and routing, by the first sessionserver and to the second session server, the message.
 2. The method ofclaim 1, wherein the determining the second session server comprises:determining, based on the message, that the first session server doesnot comprise a virtual gateway associated with the premises managementsystem.
 3. The method of claim 1, further comprising: causing, by thefirst session server and based on the first message, execution of thefirst virtual gateway on the second session server.
 4. The method ofclaim 1, wherein the determining the second session server comprises:broadcasting, by the first session server and to the other sessionservers of the plurality of session servers, a request for a returnresponse indicating that the respective session server comprises avirtual gateway associated with the premises management system; andreceiving, by the first session server and from the second sessionserver, a return response indicating that the second session servercomprises the first virtual gateway.
 5. The method of claim 1, furthercomprising: receiving, by the first session server and from a secondpremises device associated with a second premises management systemlocated at a second premises, a second message indicating state dataassociated with the second premises management system; determining, bythe first session server and based on the second message, that no othersession servers of the plurality of session servers comprise a virtualgateway associated with the second premises management system; andcausing, by the first session server and based on the second message,execution of a third virtual gateway, associated with the secondpremises management system, on the first session server.
 6. The methodof claim 1, wherein the first virtual gateway comprises a gateway statemachine associated with the premises management system.
 7. The method ofclaim 6, wherein the gateway state machine is configured to store themessage to maintain state data associated with the premises managementsystem.
 8. The method of claim 1, wherein the first virtual gateway isconfigured to: transmit, to a computing device located external to thepremises, the state data; and receive, from the computing device,control data for the premises management system.
 9. The method of claim1, wherein the message comprises a User Datagram Protocol (UDP) message.10. The method of claim 1, wherein the first session server and thepremises management system are configured to communicate via apersistent network connection between the first session server and thepremises management system.
 11. The method of claim 10, wherein thepersistent network connection comprises a Transmission Control Protocol(TCP) connection.
 12. The method of claim 1, wherein the receiving themessage comprises: receiving, via at least one of a security panellocated at the premises or a network device located at the premises, themessage.
 13. The method of claim 1, wherein the state data is associatedwith at least one of a sensor, a detector, a camera, a touchscreencontroller, a video camera, an input/output (I/O) device, an actuator, adevice controller, a premises gateway, a network device, a networkrouter, or a security panel.
 14. A first session server devicecomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the firstsession server device to: receive, from a premises management systemlocated at a premises, a message indicating state data associated withthe premises management system; determine, based on the message, asecond session server of a plurality of session servers located externalto the premises, wherein each session server of the plurality of sessionservers is configured to host one or more virtual gateways, the secondsession server hosting a first virtual gateway associated with thepremises management system; determine, based on the first message, athird session server of the plurality of session servers hosting asecond virtual gateway associated with the premises management system;cause, by the first session server device, shutdown of the secondvirtual gateway on the third session server; and route, to the secondsession server, the message.
 15. The device of claim 14, wherein thedevice comprises multiple session servers of the plurality of sessionservers.
 16. The device of claim 14, wherein the instructions, whenexecuted by the one or more processors, further cause the device to:determine the first session server by determining, based on the message,that the device does not comprise a virtual gateway associated with thepremises management system.
 17. The device of claim 14, wherein theinstructions, when executed by the one or more processors, further causethe device to: cause, based on the message, execution of the firstvirtual gateway on the first session server.
 18. The device of claim 14,wherein the instructions, when executed by the one or more processors,further cause the device to: determine the second session server by:broadcasting, to the plurality of session servers, a request for areturn response indicating that the respective session server comprisesa virtual gateway associated with the premises management system; andreceiving, from the second session server, a return response indicatingthat the second session server comprises the first virtual gateway. 19.The device of claim 14, wherein the instructions, when executed by theone or more processors, further cause the device to: receive, from asecond premises management system located at a second premises, a secondmessage indicating state data associated with the second premisesmanagement system; determine, based on the second message, that no othersession servers of the plurality of session servers comprise a virtualgateway associated with the second premises management system; andcause, based on the second message, execution of a third virtualgateway, associated with the second premises management system, on thedevice.
 20. A system comprising: a plurality of premises devicesassociated with a premises management system located at a premises; anda first session server of a plurality of session servers, wherein theplurality of session servers are located external to the premises andwherein each one of the plurality of session servers is configured tohost one or more virtual gateways, wherein the first session server isconfigured to: receive, from a premises device of the plurality ofpremises devices, a message indicating state data associated with thepremises management system; determine, based on the message, a secondsession server of the plurality of session servers hosting a firstvirtual gateway of the one or more virtual gateways that is associatedwith the premises management system; determine, based on the firstmessage, a third session server of the plurality of session servershosting a second virtual gateway associated with the premises managementsystem; cause, by the first session server, shutdown of the secondvirtual gateway on the third session server; and route, to the secondsession server, the message.
 21. The system of claim 20, wherein thefirst session server is further configured to: determine the secondsession server by determining, based on the message, that the firstsession server does not comprise a virtual gateway associated with thepremises management system.
 22. The system of claim 20, wherein thefirst session server is further configured to: cause, based on themessage, execution of the first virtual gateway on the second sessionserver.
 23. The system of claim 20, wherein the first session server isfurther configured to: determine the second session server by:broadcasting, to the other session servers of the plurality of sessionservers, a request for a return response indicating that the respectivesession server comprises a virtual gateway associated with the premisesmanagement system; and receiving, from the second session server, areturn response indicating that the second session server comprises thefirst virtual gateway.
 24. The system of claim 20, wherein the firstsession server is further configured to: receive, from a second premisesdevice associated with a second premises management system located at asecond premises, a second message indicating state data associated withthe second premises management system; determine, based on the secondmessage, that no other session servers of the plurality of sessionservers comprise a virtual gateway associated with the second premisesmanagement system; and cause, based on the second message, execution ofa third virtual gateway, associated with the second premises managementsystem, on the first session server.
 25. The system of claim 20, whereinthe first virtual gateway comprises a gateway state machine associatedwith the premises management system.
 26. The system of claim 25, whereinthe gateway state machine is configured to store the message to maintainstate data associated with the premises management system.
 27. Thesystem of claim 20, wherein the first virtual gateway is configured to:transmit, to a computing device located external to the premises, thestate data; and receive, from the computing device, control data for thepremises management system.
 28. A non-transitory computer-readablemedium storing instructions that, when executed, cause: receiving, by afirst session server of a plurality of session servers located externalto a premises, wherein each session server of the plurality of sessionservers is configured to host one or more virtual gateways, and from apremises management system located at the premises, a message indicatingstate data associated with the premises management system; determining,by the first session server and based on the message, a second sessionserver of the plurality of session servers hosting a first virtualgateway associated with the premises management system; determining, bythe first session server and based on the first message, a third sessionserver of the plurality of session servers hosting a second virtualgateway associated with the premises management system; causing, by thefirst session server, shutdown of the second virtual gateway on thethird session server; and routing, by the first session server and tothe second session server, the message.
 29. The non-transitorycomputer-readable medium of claim 28, wherein the determining the secondsession server comprises: determining, based on the message, that thefirst session server does not comprise a virtual gateway associated withthe premises management system.
 30. The non-transitory computer-readablemedium of claim 28, wherein the determining the second session servercomprises: broadcasting, by the first session server and to the othersession servers of the plurality of session servers, a request for areturn response indicating that the respective session server comprisesa virtual gateway associated with the premises management system; andreceiving, by the first session server and from the second sessionserver, a return response indicating that the second session servercomprises the first virtual gateway.
 31. The non-transitorycomputer-readable medium of claim 28, wherein the instructions, whenexecuted, further cause: causing, by the first session server and basedon the message, execution of the first virtual gateway on the secondsession server.
 32. The non-transitory computer-readable medium of claim28, wherein the instructions, when executed, further cause: receiving,by the first session server and from a second premises device associatedwith a second premises management system located at a second premises, asecond message indicating state data associated with the second premisesmanagement system; determining, by the first session server and based onthe second message, that no other session servers of the plurality ofsession servers comprise a virtual gateway associated with the secondpremises management system; and causing, by the first session server andbased on the second message, execution of a third virtual gateway,associated with the second premises management system, on the firstsession server.